Inter layer prediction with different coding block size

ABSTRACT

Several techniques for video encoding and video decoding are described. One example method includes performing a conversion between a video unit of a current picture of a video and a bitstream of the video according to a rule. The rule specifies that, for a given picture to be available as a reference picture whose motion information is used for the conversion, the given picture has a same coding tree unit size or a same coding tree block size as the current picture.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Patent Application No. PCT/CN2021/100316, filed on Jun. 16, 2021, which claims the priority to and benefits of International Patent Application No. PCT/CN2020/097293, filed on Jun. 20, 2020. All the aforementioned patent applications are hereby incorporated by reference in their entireties.

TECHNICAL FIELD

This patent document relates to image and video coding and decoding.

BACKGROUND

Digital video accounts for the largest bandwidth use on the internet and other digital communication networks. As the number of connected user devices capable of receiving and displaying video increases, it is expected that the bandwidth demand for digital video usage will continue to grow.

SUMMARY

The present document discloses techniques that can be used by video encoders and decoders for processing coded representation of video using control information useful for decoding of the coded representation.

In one example aspect, a method of processing video data includes performing a conversion between a video unit of a current picture of a video and a bitstream of the video according to a rule, The rule specifies that, for a given picture to be available as a reference picture whose motion information is used for the conversion, the given picture has a same coding tree unit size or a same coding tree block size as the current picture.

In another example aspect, a video processing method is disclosed. The method includes performing a conversion between a video comprising one or more video pictures, wherein the coded representation conforms to a format rule; wherein the format rule specifies that two or more syntax fields in a sequence parameter set controls a reference picture resolution (RPR) change in the video.

In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video comprising one or more video pictures, wherein the coded representation conforms to a format rule; wherein the format rule specifies that a single syntax field in a sequence parameter set controls a reference picture resolution (RPR) change in the video; and wherein, the format rule specifies that, irrespective of a value of the single syntax field, resampling of an inter-layer reference picture is permitted for the conversion.

In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video comprising one or more layers comprising one or more video pictures comprising one or more subpictures, wherein the coded representation conforms to a format rule; wherein the format rule specifies a first constraint on a cross-layer alignment or a second constraint on a combination of subpictures and scalability of inter-layer pictures.

In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video comprising one or more layers comprising one or more video pictures comprising one or more subpictures, wherein the conversion conforms to a format rule that specifies that an inter-layer reference picture or a long term reference picture is disallowed from being a collocated picture of a current picture for the conversion.

In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video comprising multiple pictures and a coded representation of the video, wherein the conversion conforms to a rule that specifies that values of each of scaling_win_left_offset, scaling_win_right_offset, scaling_win_top_offset, and scaling_win_bottom_offset are same for any two pictures within a same coded layer video sequence or coded video sequence having the same values of pic width in luma samples and pic_height_in_luma_samples.

In another example aspect, another video processing method is disclosed. The method includes performing a conversion between a video comprising multiple pictures and a coded representation of the video, wherein the conversion conforms to a rule that specifies that in case that a picture resolution or a scaling window is different for a current picture and other picture in a same access unit, then inter-layer prediction is only allowed when the current picture is an intra random access point picture.

In another example aspect, another video processing method is disclosed. The method includes determining, for a conversion between video blocks of a current picture of a video and a coded representation of the video, whether a rule is to be applied based on a first size of the video blocks compared to a second size of video blocks in a collocated video picture or an inter-layer picture, and performing the conversion based on the determining.

In yet another example aspect, a video encoder apparatus is disclosed. The video encoder comprises a processor configured to implement above-described methods.

In yet another example aspect, a video decoder apparatus is disclosed. The video decoder comprises a processor configured to implement above-described methods.

In yet another example aspect, a computer readable medium having code stored thereon is disclose. The code embodies one of the methods described herein in the form of processor-executable code.

These, and other, features are described throughout the present document.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows an example of raster-scan slice partitioning of a picture, where the picture is divided into 12 tiles and 3 raster-scan slices.

FIG. 2 shows an example of rectangular slice partitioning of a picture, where the picture is divided into 24 tiles (6 tile columns and 4 tile rows) and 9 rectangular slices.

FIG. 3 shows an example of a picture partitioned into tiles and rectangular slices, where the picture is divided into 4 tiles (2 tile columns and 2 tile rows) and 4 rectangular slices.

FIG. 4 shows a picture that is partitioned into 15 tiles, 24 slices and 24 subpictures.

FIG. 5 is a block diagram of an example video processing system.

FIG. 6 is a block diagram of a video processing apparatus.

FIG. 7 is a flowchart for an example method of video processing.

FIG. 8 is a block diagram that illustrates a video coding system in accordance with some embodiments of the present disclosure.

FIG. 9 is a block diagram that illustrates an encoder in accordance with some embodiments of the present disclosure.

FIG. 10 is a block diagram that illustrates a decoder in accordance with some embodiments of the present disclosure.

FIG. 11 shows an example of a typical subpicture-based viewport-dependent 360° video coding scheme.

FIG. 12 shows a viewport-dependent 360° video coding scheme based on subpictures and spatial scalability.

FIG. 13 is a flowchart representation of a method for video processing in accordance with one or more embodiments of the present technology.

DETAILED DESCRIPTION

Section headings are used in the present document for ease of understanding and do not limit the applicability of techniques and embodiments disclosed in each section only to that section. Furthermore, H.266 terminology is used in some description only for ease of understanding and not for limiting scope of the disclosed techniques. As such, the techniques described herein are applicable to other video codec protocols and designs also. In the present document, editing changes are shown to text by strikethrough indicating cancelled text and highlight indicating added text (including boldface italic), with respect to the current draft of the VVC specification.

1. Overview

This document is related to video coding technologies. Specifically, it is about 1) the combination of two or more of reference picture resampling (RPR), subpictures, and scalability in video coding, 2) the use of RPR between a current picture and a reference pictures that have the same spatial resolution, and 3) the combination of long-term reference picture and collocated picture. The ideas may be applied individually or in various combination, to any video coding standard or non-standard video codec that supports multi-layer video coding, e.g., the being-developed Versatile Video Coding (VVC).

2. Abbreviations

APS Adaptation Parameter Set

AU Access Unit

AUD Access Unit Delimiter

AVC Advanced Video Coding

CLVS Coded Layer Video Sequence

CCALF Cross-Component Adaptive Loop Filter

CPB Coded Picture Buffer

CRA Clean Random Access

CTU Coding Tree Unit

CVS Coded Video Sequence

DCI Decoding Capability Information

DPB Decoded Picture Buffer

EOB End Of Bitstream

EOS End Of Sequence

GDR Gradual Decoding Refresh

HEVC High Efficiency Video Coding

HRD Hypothetical Reference Decoder

IDR Instantaneous Decoding Refresh

ILP Inter-Layer Prediction

ILRP Inter-Layer Reference Picture

IRAP Intra Random Access Picture

JEM Joint Exploration Model

LTRP Long-Term Reference Picture

MCTS Motion-Constrained Tile Sets

NAL Network Abstraction Layer

OLS Output Layer Set

PH Picture Header

PPS Picture Parameter Set

PTL Profile, Tier and Level

PU Picture Unit

RAP Random Access Point

RBSP Raw Byte Sequence Payload

SEI Supplemental Enhancement Information

SPS Sequence Parameter Set

STRP Short-Term Reference Picture

SVC Scalable Video Coding

VCL Video Coding Layer

VPS Video Parameter Set

VTM VVC Test Model

VUI Video Usability Information

VVC Versatile Video Coding

3. Initial Discussion

Video coding standards have evolved primarily through the development of the well-known ITU-T and ISO/IEC standards. The ITU-T produced H.261 and H.263, ISO/IEC produced MPEG-1 and MPEG-4 Visual, and the two organizations jointly produced the H.262/MPEG-2 Video and H.264/MPEG-4 Advanced Video Coding (AVC) and H.265/HEVC standards. Since H.262, the video coding standards are based on the hybrid video coding structure wherein temporal prediction plus transform coding are utilized. To explore the future video coding technologies beyond HEVC, the Joint Video Exploration Team (WET) was founded by VCEG and MPEG jointly in 2015. Since then, many new methods have been adopted by JVET and put into the reference software named Joint Exploration Model (JEM). The JVET meeting is concurrently held once every quarter, and the new coding standard is targeting at 50% bitrate reduction as compared to HEVC. The new video coding standard was officially named as Versatile Video Coding (VVC) in the April 2018 JVET meeting, and the first version of VVC test model (VTM) was released at that time. As there are continuous effort contributing to VVC standardization, new coding techniques are being adopted to the VVC standard in every JVET meeting. The VVC working draft and test model VTM are then updated after every meeting. The VVC project is now aiming for technical completion (FDIS) at the July 2020 meeting.

3.1. Picture Partitioning Schemes in HEVC

HEVC includes four different picture partitioning schemes, namely regular slices, dependent slices, tiles, and Wavefront Parallel Processing (WPP), which may be applied for Maximum Transfer Unit (MTU) size matching, parallel processing, and reduced end-to-end delay.

Regular slices are similar as in H.264/AVC. Each regular slice is encapsulated in its own NAL unit, and in-picture prediction (intra sample prediction, motion information prediction, coding mode prediction) and entropy coding dependency across slice boundaries are disabled. Thus a regular slice can be reconstructed independently from other regular slices within the same picture (though there may still have interdependencies due to loop filtering operations).

The regular slice is the only tool that can be used for parallelization that is also available, in virtually identical form, in H.264/AVC. Regular slices based parallelization does not require much inter-processor or inter-core communication (except for inter-processor or inter-core data sharing for motion compensation when decoding a predictively coded picture, which is typically much heavier than inter-processor or inter-core data sharing due to in-picture prediction). However, for the same reason, the use of regular slices can incur substantial coding overhead due to the bit cost of the slice header and due to the lack of prediction across the slice boundaries. Further, regular slices (in contrast to the other tools mentioned below) also serve as the key mechanism for bitstream partitioning to match MTU size requirements, due to the in-picture independence of regular slices and that each regular slice is encapsulated in its own NAL unit. In many cases, the goal of parallelization and the goal of MTU size matching place contradicting demands to the slice layout in a picture. The realization of this situation led to the development of the parallelization tools mentioned below.

Dependent slices have short slice headers and allow partitioning of the bitstream at treeblock boundaries without breaking any in-picture prediction. Basically, dependent slices provide fragmentation of regular slices into multiple NAL units, to provide reduced end-to-end delay by allowing a part of a regular slice to be sent out before the encoding of the entire regular slice is finished.

In WPP, the picture is partitioned into single rows of coding tree blocks (CTBs). Entropy decoding and prediction are allowed to use data from CTBs in other partitions. Parallel processing is possible through parallel decoding of CTB rows, where the start of the decoding of a CTB row is delayed by two CTBs, so to ensure that data related to a CTB above and to the right of the subject CTB is available before the subject CTB is being decoded. Using this staggered start (which appears like a wavefront when represented graphically), parallelization is possible with up to as many processors/cores as the picture contains CTB rows. Because in-picture prediction between neighboring treeblock rows within a picture is permitted, the required inter-processor/inter-core communication to enable in-picture prediction can be substantial. The WPP partitioning does not result in the production of additional NAL units compared to when it is not applied, thus WPP is not a tool for MTU size matching. However, if MTU size matching is required, regular slices can be used with WPP, with certain coding overhead.

Tiles define horizontal and vertical boundaries that partition a picture into tile columns and rows. Tile column runs from the top of a picture to the bottom of the picture. Likewise, tile row runs from the left of the picture to the right of the picture. The number of tiles in a picture can be derived simply as number of tile columns multiply by number of tile rows.

The scan order of CTBs is changed to be local within a tile (in the order of a CTB raster scan of a tile), before decoding the top-left CTB of the next tile in the order of tile raster scan of a picture. Similar to regular slices, tiles break in-picture prediction dependencies as well as entropy decoding dependencies. However, they do not need to be included into individual NAL units (same as WPP in this regard); hence tiles cannot be used for MTU size matching. Each tile can be processed by one processor/core, and the inter-processor/inter-core communication required for in-picture prediction between processing units decoding neighboring tiles is limited to conveying the shared slice header in cases a slice is spanning more than one tile, and loop filtering related sharing of reconstructed samples and metadata. When more than one tile or WPP segment is included in a slice, the entry point byte offset for each tile or WPP segment other than the first one in the slice is signaled in the slice header.

For simplicity, restrictions on the application of the four different picture partitioning schemes have been specified in HEVC. A given coded video sequence cannot include both tiles and wavefronts for most of the profiles specified in HEVC. For each slice and tile, either or both of the following conditions must be fulfilled: 1) all coded treeblocks in a slice belong to the same tile; 2) all coded treeblocks in a tile belong to the same slice. Finally, a wavefront segment contains exactly one CTB row, and when WPP is in use, if a slice starts within a CTB row, it must end in the same CTB row.

With a recent amendment to HEVC, HEVC specifies three MCTS-related SEI messages, namely temporal MCTSs SEI message, MCTSs extraction information set SEI message, and MCTSs extraction information nesting SEI message.

The temporal MCTSs SEI message indicates existence of MCTSs in the bitstream and signals the MCTSs. For each MCTS, motion vectors are restricted to point to full-sample locations inside the MCTS and to fractional-sample locations that require only full-sample locations inside the MCTS for interpolation, and the usage of motion vector candidates for temporal motion vector prediction derived from blocks outside the MCTS is disallowed. This way, each MCTS may be independently decoded without the existence of tiles not included in the MCTS.

The MCTSs extraction information sets SEI message provides supplemental information that can be used in the MCTS sub-bitstream extraction (specified as part of the semantics of the SEI message) to generate a conforming bitstream for an MCTS set. The information consists of a number of extraction information sets, each defining a number of MCTS sets and containing RBSP bytes of the replacement VPSs, SPSs, and PPSs to be used during the MCTS sub-bitstream extraction process. When extracting a sub-bitstream according to the MCTS sub-bitstream extraction process, parameter sets (VPSs, SPSs, and PPSs) need to be rewritten or replaced, slice headers need to be slightly updated because one or all of the slice address related syntax elements (including first_slice_segment_in_pic_fla and slice_segment_address) typically would need to have different values.

3.2. Partitioning of Pictures in VVC

In VVC, A picture is divided into one or more tile rows and one or more tile columns. A tile is a sequence of CTUs that covers a rectangular region of a picture. The CTUs in a tile are scanned in raster scan order within that tile.

A slice consists of an integer number of complete tiles or an integer number of consecutive complete CTU rows within a tile of a picture.

Two modes of slices are supported, namely the raster-scan slice mode and the rectangular slice mode. In the raster-scan slice mode, a slice contains a sequence of complete tiles in a tile raster scan of a picture. In the rectangular slice mode, a slice contains either a number of complete tiles that collectively form a rectangular region of the picture or a number of consecutive complete CTU rows of one tile that collectively form a rectangular region of the picture. Tiles within a rectangular slice are scanned in tile raster scan order within the rectangular region corresponding to that slice.

A subpicture contains one or more slices that collectively cover a rectangular region of a picture.

FIG. 1 shows an example of raster-scan slice partitioning of a picture, where the picture is divided into 12 tiles and 3 raster-scan slices.

FIG. 2 shows an example of rectangular slice partitioning of a picture, where the picture is divided into 24 tiles (6 tile columns and 4 tile rows) and 9 rectangular slices.

FIG. 3 shows an example of a picture partitioned into tiles and rectangular slices, where the picture is divided into 4 tiles (2 tile columns and 2 tile rows) and 4 rectangular slices.

FIG. 4 shows an example of subpicture partitioning of a picture, where a picture is partitioned into 18 tiles, 12 on the left-hand side each covering one slice of 4 by 4 CTUs and 6 tiles on the right-hand side each covering 2 vertically-stacked slices of 2 by 2 CTUs, altogether resulting in 24 slices and 24 subpictures of varying dimensions (each slice is a subpicture).

3.3. Picture Resolution Change Within a Sequence

In AVC and HEVC, the spatial resolution of pictures cannot change unless a new sequence using a new SPS starts, with an IRAP picture. VVC enables picture resolution change within a sequence at a position without encoding an IRAP picture, which is always intra-coded. This feature is sometimes referred to as reference picture resampling (RPR), as the feature needs resampling of a reference picture used for inter prediction when that reference picture has a different resolution than the current picture being decoded.

The scaling ratio is restricted to be larger than or equal to 1/2 (2 times downsampling from the reference picture to the current picture), and less than or equal to 8 (8 times upsampling). Three sets of resampling filters with different frequency cutoffs are specified to handle various scaling ratios between a reference picture and the current picture. The three sets of resampling filters are applied respectively for the scaling ratio ranging from 1/2to 1/1.75, from 1/1.75 to 1/1.25, and from 1/1.25 to 8. Each set of resampling filters has 16 phases for luma and 32 phases for chroma which is same to the case of motion compensation interpolation filters. Actually the normal MC interpolation process is a special case of the resampling process with scaling ratio ranging from 1/1.25 to 8. The horizontal and vertical scaling ratios are derived based on picture width and height, and the left, right, top and bottom scaling offsets specified for the reference picture and the current picture.

Other aspects of the VVC design for support of this feature that are different from HEVC include: i) The picture resolution and the corresponding conformance window are signaled in the PPS instead of in the SPS, while in the SPS the maximum picture resolution is signaled. ii) For a single-layer bitstream, each picture store (a slot in the DPB for storage of one decoded picture) occupies the buffer size as required for storing a decoded picture having the maximum picture resolution.

3.4. Scalable Video Coding (SVC) in General and in VVC

Scalable video coding (SVC, sometimes also just referred to as scalability in video coding) refers to video coding in which a base layer (BL), sometimes referred to as a reference layer (RL), and one or more scalable enhancement layers (ELs) are used. In SVC, the base layer can carry video data with a base level of quality. The one or more enhancement layers can carry additional video data to support, for example, higher spatial, temporal, and/or signal-to-noise (SNR) levels. Enhancement layers may be defined relative to a previously encoded layer. For example, a bottom layer may serve as a BL, while a top layer may serve as an EL. Middle layers may serve as either ELs or RLs, or both. For example, a middle layer (e.g., a layer that is neither the lowest layer nor the highest layer) may be an EL for the layers below the middle layer, such as the base layer or any intervening enhancement layers, and at the same time serve as a RL for one or more enhancement layers above the middle layer. Similarly, in the Multiview or 3D extension of the HEVC standard, there may be multiple views, and information of one view may be utilized to code (e.g., encode or decode) the information of another view (e.g., motion estimation, motion vector prediction and/or other redundancies).

In SVC, the parameters used by the encoder or the decoder are grouped into parameter sets based on the coding level (e.g., video-level, sequence-level, picture-level, slice level, etc.) in which they may be utilized. For example, parameters that may be utilized by one or more coded video sequences of different layers in the bitstream may be included in a video parameter set (VPS), and parameters that are utilized by one or more pictures in a coded video sequence may be included in a sequence parameter set (SPS). Similarly, parameters that are utilized by one or more slices in a picture may be included in a picture parameter set (PPS), and other parameters that are specific to a single slice may be included in a slice header. Similarly, the indication of which parameter set(s) a particular layer is using at a given time may be provided at various coding levels.

Thanks to the support of reference picture resampling (RPR) in VVC, support of a bitstream containing multiple layers, e.g., two layers with SD and HD resolutions in VVC can be designed without the need any additional signal-processing-level coding tool, as upsampling needed for spatial scalability support can just use the RPR upsampling filter. Nevertheless, high-level syntax changes (compared to not supporting scalability) are needed for scalability support. Scalability support is specified in VVC version 1. Different from the scalability supports in any earlier video coding standards, including in extensions of AVC and HEVC, the design of VVC scalability has been made friendly to single-layer decoder designs as much as possible. The decoding capability for multi-layer bitstreams are specified in a manner as if there were only a single layer in the bitstream. E.g., the decoding capability, such as DPB size, is specified in a manner that is independent of the number of layers in the bitstream to be decoded. Basically, a decoder designed for single-layer bitstreams does not need much change to be able to decode multi-layer bitstreams. Compared to the designs of multi-layer extensions of AVC and HEVC, the HLS aspects have been significantly simplified at the sacrifice of some flexibilities. For example, an TRAP AU is required to contain a picture for each of the layers present in the CVS.

3.5. Viewport-Dependent 360° Video Streaming Based on Subpicures

In streaming of 360° video, a.k.a. omnidirectional video, at any particular moment only a subset (e.g., the current viewport) of the entire omnidirectional video sphere would be rendered to the user, while the user can turn his/her head anytime to change the viewing orientation and consequently the current viewport. While it is desirable to have at least some lower-quality representation of the area not covered by the current viewport available at the client and ready to be rendered to the user just in case the user suddenly changes his/her viewing orientation to anywhere on the sphere, a high-quality representation of the omnidirectional video is only needed for the current viewport that is being rendered to the use right now. Splitting the high-quality representation of the entire omnidirectional video into subpictures at an appropriate granularity enables such an optimization. Using VVC, the two representations can be encoded as two layers that are independent from each other.

A typical subpicture-based viewport-dependent 360° video delivery scheme is shown in FIG. 11 wherein a higher-resolution representation of the full video consists of subpictures, while a lower-resolution representation of the full video does not use subpictures and can be coded with less frequent random access points than the higher-resolution representation. The client receives the full video in the lower-resolution and for the higher-resolution video it only receives and decode the subpictures that cover the current viewport.

3.6. Parameter Sets

AVC, HEVC, and VVC specify parameter sets. The types of parameter sets include SPS, PPS, APS, and VPS. SPS and PPS are supported in all of AVC, HEVC, and VVC. VPS was introduced since HEVC and is included in both HEVC and VVC. APS was not included in AVC or HEVC but is included in the latest VVC draft text.

SPS was designed to carry sequence-level header information, and PPS was designed to carry infrequently changing picture-level header information. With SPS and PPS, infrequently changing information need not to be repeated for each sequence or picture, hence redundant signaling of this information can be avoided. Furthermore, the use of SPS and PPS enables out-of-band transmission of the important header information, thus not only avoiding the need for redundant transmissions but also improving error resilience.

VPS was introduced for carrying sequence-level header information that is common for all layers in multi-layer bitstreams.

APS was introduced for carrying such picture-level or slice-level information that needs quite some bits to code, can be shared by multiple pictures, and in a sequence there can be quite many different variations.

The followings are semantics of SPS/PPS/APS in some embodiments:

sps_seqparameter_set_id provides an identifier for the SPS for reference by other syntax elements. SPS NAL units, regardless of the nuh_layer_id values, share the same value space of sps_sec_parameter_set_id. Let spsLayerId be the value of the nuh_layer_id of a particular SPS NAL unit, and vclLayerId be the value of the nuhlayer_id of a particular VCL NAL unit. The particular VCL NAL unit shall not refer to the particular SPS NAL unit unless spsLayerId is less than or equal to vclLayerId and the OLS being decoded contains both the layer with nuh_layer_id equal to spsLayerId and the layer with nuh_layer_id equal to vclLayerId. pps_pic_parameter_set_id identifies the PPS for reference by other syntax elements. The value of pps_pic_parameter_set_id shall be in the range of 0 to 63, inclusive. PPS NAL units, regardless of the nuh_layer_id values, share the same value space of pps_pic_parameter_set_id. Let ppsLayerId be the value of the nuh_layer_id of a particular PPS NAL unit, and vclLayerld be the value of the nuhlayer_id of a particular VCL NAL unit. The particular VCL NAL unit shall not refer to the particular PPS NAL unit unless ppsLayerld is less than or equal to vclLayerld and the OLS being decoded contains both the layer with nuhlayer_id equal to ppsLayerld and the layer with nuh_layer_id equal to vclLayerld. adaptation_parameter_set_id provides an identifier for the APS for reference by other syntax elements. When aps_params_type is equal to ALF_APS or SCALING_APS, the value of adaptation_parameter_set_id shall be in the range of 0 to 7, inclusive. When aps_params_type is equal to LMCS_APS, the value of adaptation_parameter_set_id shall be in the range of 0 to 3, inclusive. Let apsLayerld be the value of the nuh_layer_id of a particular APS NAL unit, and vclLayerld be the value of the nuhlayer_id of a particular VCL NAL unit. The particular VCL NAL unit shall not refer to the particular APS NAL unit unless apsLayerId is less than or equal to vclLayerId and the OLS being decoded contains both the layer with nuhlayer_id equal to apsLayerId and the layer with nuh_layer_id equal to vclLayerId.

3.7. Sub-Bitstream Extraction Process

Inputs to this process are a bitstream inBitstream, a target OLS index targetOlsIdx, and a target highest TemporalId value tIdTarget.

Output of this process is a sub-bitstream outBitstream.

It is a requirement of bitstream conformance for the input bitstream that any output sub-bitstream that satisfies all of the following conditions shall be a conforming bitstream:

-   The output sub-bitstream is the output of the process specified in     this clause with the bitstream, targetOlsldx equal to an index to     the list of OLSs specified by the VPS, and tIdTarget equal to any     value in the range of 0 to 6, inclusive, as inputs. -   The output sub-bitstream contains at least one VCL NAL unit with     nuh_layer_id equal to each of the nuh_layer_id values in     LayerIdInOls[targetOlsldx]. -   The output sub-bitstream contains at least one VCL NAL unit with     TemporalId equal to tIdTarget.     -   NOTE—A conforming bitstream contains one or more coded slice NAL         units with TemporalId equal to 0, but does not have to contain         coded slice NAL units with nuh_layer_id equal to 0.         The output sub-bitstream OutBitstream is derived as follows: -   The bitstream outBitstream is set to be identical to the bitstream     inBitstream. -   Remove from outBitstream all NAL units with TemporalId greater than     tIdTarget. -   Remove from outBitstream all NAL units with nal_unit_type not equal     to any of VPS_NUT, DCI_NUT, and EOB_NUT and with nuhlayerjd not     included in the list LayerIdInOls[targetOlsldx]. -   Remove from outBitstream all NAL units for which all of the     following conditions are true:     -   nal_unit_type is not equal to IDR_W_RADL, IDR_N_LP, or CRA_NUT.     -   nuhlayer_id is equal to LayerIdInOls[targetOlsIdx] [j] for a         value of j in the range of 0 to NumLayersInOls[targetOlsldx] — 1         inclusive.     -   TemporalId is greater than or equal to         NumSubLayersInLayerInOLS[targetOlsldx][j]. -   Remove from outBitstream all SEI NAL units that contain a scalable     nesting SEI message that has nesting_ols_flag equal to 1 and there     is no value of i in the range of 0 to nesting_num_olss_minus 1,     inclusive, such that NestingOlsIdx[i] is equal to targetOlsIdx. -   When LayerIdInOls[targetOlsldx] does not include all values of     nuh_layer_id in all NAL units in the bitstream, the following     applies:     -   Remove from outBitstream all SEI NAL units that contain a         non-scalable-nested SEI message with payloadType equal to 0         (buffering period) or 130 (decoding unit information).     -   When general_same_pic_timing_in_all_ols_flag is equal to 0,         remove from outBitstream all SEI NAL units that contain a         non-scalable-nested SEI message with payloadType equal to 1         (picture timing).     -   When outBitstream contains SEI NAL units that contain a scalable         nesting SEI message with nesting_ols_flag equal to 1 and are         applicable to outBitstream (NestingOlsIdx[i] is equal to         targetOlsIdx), the following applies:         -   If same_pic_timing_within_ols_flag is equal to 0, extract             appropriate non-scalable-nested SEI message with payloadType             equal to 0 (buffering period), 1 (picture timing), or 130             (decoding unit information) from the scalable nesting SEI             message and include those SEI messages in outBitstream.         -   Otherwise (same_pic_timing_within_ols_flag is equal to 1),             extract appropriate non-scalable-nested SEI message with             payloadType equal to 0 (buffering period) or 130 (decoding             unit information) from the scalable nesting SEI message and             include those SEI messages in outBitstream.

4. Technical Problems Solved by Disclosed Technical Solutions

The existing design in the latest VVC text has the following problems:

-   1) The current VVC design supports the typical coding scheme for     360° video as shown in FIG. 11 . However, although scalability is     supported in the current VVC design, an improved 360° video coding     scheme as shown in FIG. 12 is not supported. The only difference     compared to the approach shown in FIG. 11 is that inter-layer     prediction (ILP) is applied for the approach shown in FIG. 12 .     The following two places in the VVC draft disallows the combined use     of subpicures and spatial scalability:     -   a. The spatial scalability design in VVC relies on the RPR         feature. However, the combination of RPR and subpictures is         currently disallowed by the following semantics constraint:         -   When res_change_in_clvs_allowed_flag is equal to 1, the             value of subpic_info_present_flag shall be equal to 0.     -    Consequenity, the improved coding scheme is disallowed, because         for the SPS referred to by the higher layer, the above constrain         disallows setting subpic infopresent flag to 1 (to use mutiple         subpictures per picture) and at the same time set res change in         clvs allowed flag to 1 (to enable RPR, which is needed for         spatial scalability with ILP).     -   b. The current VVC draft has the following constraint on the         combination of subpictures and scalability:         -   When subpic_treated_as_pic_flag[i] is equal to 1, it is a             requirement of bitstream conformance that all of the             following conditions are true for each output layer and its             reference layers in an OLS that includes the layer             containing the i-th subpicture as an output layer:         -   All pictures in the output layer and its reference layers             shall have the same value of picwidthinluma samples and the             same value of pic_height_in_luma_samples.         -   All the SPSs referred to by the output layer and its             reference layers shall have the same value of             sps_num_subpics_minus1 and shall have the same values of             subpic_ctu_top_left_x[j], subpic_ctu_top_lef_ty[j],             subpic_width_minus1[j], subpic_height_minus1[j], and             loop_filter_across_subpic_enabled_flag[j], respectively, for             each value of j in the range of 0 to sps_num_subpics_minus1,             inclusive.         -   All pictures in each access unit in the output layer and its             reference layers shall have the same value of SubpicIdVal[j]             for each value of j in the range of 0 to             sps_num_subpics_minus1, inclusive.         -   This above constraint basically disallows any other             combination of subpictures and scalability with ILP than the             restricted combination of subpictures with SNR scalability,             wherein layers within each dependency tree must have the             same spatial resolution as well as the same subpicture             layout. -   2) When subpic_treated_as_pic_flag[i] is equal to 1, the subpicture     boundaries of the i-th subpicture would be treated as picture     boundaries in motion compensation. Such treating is realized in the     VVC draft text by applying certain clipping operations in the     decoding processes related to motion compensation. However, for the     improved coding scheme shown in FIG. 12 since the lower layer is     fully available to the decoder, not just the area corrsponding to     the i-th subpicture, such clipping does not need to be applied in     this case, to avoid unnecessary coding efficiency loss. -   3) Without considering the support of the improved coding scheme     shown in FIG. 12 , the above existing constraint on the combination     of subpictures and scalability with ILP (the description is included     in the description of problem lb) has the following issues:     -   a. The constraint should also apply when the layer containing         the i-th subpicture is not an output layer of an OLS. The entire         constraint should be specified in a manner that does not taking         into account of whether a layer is an output layer of an OLS.     -   b. The requirement for the value of         subpic_treated_as_pic_flag[i] to be aligned across layers should         be included, otherwise extraction of the subpicture sequence         with the same index across the layers won't be possible.     -   c. The requirement for the value of         loop_filter_across_subpic_enabled_flag[i] to be aligned across         layers should be excluded, as regardless of the value of this         flag, as long as the subpic_treated_as_pic_flag[i] is equal to 1         the subpicture sequence is extractable. Setting of the value of         loop_filter_across_subpic_enabled_flag[i] should be left for the         encoder to decide for trading-off the quality of single         extractable subpicture sequences vs the quality of sets of         extractable subpicture sequences, just as why the two flags are         signaled independently from each other.     -   d. The entire constraint should only apply when         sps_num_subpics_minus1 is greater than 0, to avoid all cases of         one subpicture per subpicture being covered by the constraint,         unintentionally.     -   e. The temporal scope, e.g., the set of AUs, in which the         constraint applies needs to be clearly specified.     -   f. The requirement for the value of each of the scaling window         parameters scaling_win_left_offset, scaling_win_right_offset,         scaling_win_top_offset, and scaling_win_bottom_offset to be         aligned across layers should be included, to make sure RPR of         ITRPs is not needed when there are multiple subpictures per         picture. -   4) Currently, the collocated picture for a current picture may be a     long-term reference picture (LTRP) in the same layer as the current     picture and may also be an inter-layer reference picture (ILRP),     e.g., a reference picture in a different layer as the current     picture. However, in either case, POC based scaling of motion     vectors won't be applied, thus the coding performance due to     allowing this is expected to be very low. Consequently, it'd be     better to disallow the collocated picture for a current picture to     be an LTRP or ILRP. -   5) Currently, it is allowed for pictures with the same spatial     resolution in a CLVS to have different scaling windows. However,     that should be disallowed, as otherwise, the SPS flag for RPR and     the general constraint flag for RPR won't be able to be used to     fully disable the RPR tools. -   6) Currently, when doing the sub-bitstream extraction, the parameter     sets (SPS/PPS/VPS) of the layers that are not included in the     current/target OLS can be included in the extracted bitstream as     well. However, it is not the design intention that a slice in layerA     refer to a parameter set in layerB even when layerA and layerB are     not included in the current OLS being decoded as long as there is an     OLS defined in VPS that contains both layerA and layerB. -   7) Number of allowed APSs is dependent on the APS type. However, the     signalling of APS ID is fixed to be u(5) regardless of allowed APSs     which may waste unnecessary bits. -   8) Currently, the scaling window offset are signalled as positive     values so that only positive vertical and horizontal offsets are     supported. However, it is possible to allow signalling of negative     scaling window offsets so that negative vertical and horizontal     offsets can be derived even when the referenced picture does not     include a scaling window. And allowing a scaling factor larger than     one would beneficial for subpicture use case in 360° video coding as     well, e.g., base layer with whole 360 video content but with lower     resolution, and enhancement later with a particular viewport (like     zoom-in from the picture in base layer) coded in a higher     resolution. However, several places in the current spec should be     modified to support this feature. -   9) Currently, when the transform skip residual coding (TSRC) is     enabled, it is possible to use sign data hiding (SDH) and dependent     quantization (DQ) as well, which is violate the concept of lossless     coding. The TSRC is a mode in which quantization indices of all scan     positions of a transform block are coded. The SDH is a technique     that omits coding of a sign for a non-zero index. The DQ is a mode     in which quantization of a sample depends on state of previous     samples. -   10) When the CTU size of a collocated picture is same as that of     current picture, the memory loading could be done in a sequential     way since only motion information of blocks in the collocated CTU or     the CTU right to the collocated CTU of the collocated picture are     required to be fetched. However, due to inter-layer prediction,     wherein the collocated picture could be an inter-layer reference     picture (i.e., in a different layer), when the CTU size of the     collocated picture are different from the CTU size of the current     picture (this can happen when inter-layer prediction is used), which     would cause hardware implementation issue in terms of memory     loading.

5. A Listing of Technical Solutions and Embodiments

To solve the above problems, and others, methods as summarized below are disclosed. The items should be considered as examples to explain the general concepts and should not be interpreted in a narrow way. Furthermore, these items can be applied individually or combined in any manner.

-   1) To solve problem 1a, instead of having just one SPS flag (e.g.,     res_change_in_clvs_allowed_flag as in the current VVC draft) for     controlling RPR, multiple (such as two) SPS flags may be specified     and/or signaled for this purpose.     -   a. For example, the first flag (e.g.,         ref_pic_resampling_enabled_flag) specifies whether the use of         RPR may be needed for decoding of one or more pictures, while         the second flag (e.g., res_change_in_clvs_allowed_flag)         specifies whether the picture resolution is allowed to change         within the CLVS.     -   b. Alternatively, furthermore, the second flag is only signaled         when the first flag specifies that the use of RPR may be needed         for decoding of one or more pictures. Furthermore, when not         signaled, the value of the second flag is inferred to be the         value that specifies that the picture resolution is not allowed         to change within the CLVS.         -   i. Alternatively, the two flags are signaled independent of             each other.     -   c. Alternatively, furthermore, one more general constraint flag         is added, such that there is one general constraint flag for         each of the first and second flags.     -   d. Furthermore, the combination of multiple subpictures per         picture with res_change_in_clvs_allowed_flag equal to 1 is         disallowed, but the combination of multiple subpictures per         picture with ref_pic_resampling_enabled_flag equal to 1 is         allowed.     -   e. Furthermore, the constraint of the value of         scaling_window_explicit_signalling_flag based on the value of         res_change_in_clvs_allowed_flag is changed to be based on the         value of ref_pic_resampling_enabled_flag, as follows: When         is equal to 0, the value of         scaling_window_explicit_signalling_flag shall be equal to 0.     -   f. Alternatively, either one or all of the multiple (such as         two) flags may be signaled in the VPS instead of in the SPS.         -   i. In one example, either one or all of the multiple (such             as two) flags in the VPS apply to all layers specified by             the VPS.         -   ii. In another example, either one or all of the multiple             (such as two) flags in the VPS can each have multiple             instances signaled in the VPS and each instance applies to             all layers in one dependency tree.     -   g. In one example, each of the multiple flags are coded as an         unsigned integer using 1 bits u(1).     -   h. Alternatively, one syntax element may be signaled with a         non-binary value, e.g., in SPS/VPS to specify the usage of RPR         in decoding process and allowance of picture resolution change         within a CLVS.         -   i. In one example, when the value of the syntax element is             equal to 0, it specifies that use of RPR is not needed for             decoding of one or more pictures.         -   ii. In one example, when the value of the syntax element is             equal to 1, it specifies that use of RPR may be needed for             decoding of one or more pictures while the picture             resolution is disallowed to change within the CLVS.         -   iii. In one example, when the value of the syntax element is             equal to 2, it specifies that use of RPR may be needed for             decoding of one or more pictures while the picture             resolution is allowed to change within the CLVS.         -   iv. Alternatively, furthermore, how to signal the syntax             element may depend on whether inter-layer prediction is             allowed.         -   v. In one example, the syntax element is coded with ue(v),             indicating an unsigned integer 0-th order Exp-Golomb-coded             syntax element with the left bit first.         -   vi. In another example, the syntax element is coded as an             unsigned integer using N bits u(N), e.g., with N equal to 2. -   2) Alternatively, or in addition to item 1 for solving problem 1a,     still to have just one flag, e.g., res_change_in_clvs_allowed_flag,     but the semantics may be changed such that regardless of the value     of the flag, resampling of an inter-layer reference picture is     allowed.     -   a. In one example, the semantics may be changed to be as         follows: res_change_in_clvs_allowed_flag equal to 1 specifies         that the picture spatial resolution may change within a CLVS         referring to the SPS         res_change_in_clvs_allowed_flag equal to 0 specifies that the         picture spatial resolution does not change within any CLVS         referring to the SPS     -   b. With this change, then even when         res_change_in_clvs_allowed_flag is equal to 0, the decoding of a         subpicture/picture can still use RPR for inter-layer reference         pictures (ILRPs). -   3) To solve problem 1b, the constraint on combination of subpictures     and scalability with ILP is updated such that the constraint only     imposes cross-layer alignment restrictions on the current layer and     all the higher layers that depend on the current layer, while not on     the higher layers that do not depend on the current layer or on the     lower layers.     -   a. Alternatively, the constraint is updated to only impose         cross-layer alignment restrictions on the current layer and all         the layers that are higher than the current layer.     -   b. Alternatively, the constraint is updated to only impose         cross-layer alignment restrictions on the current layer and all         the higher layers in each OLS containing the current layer.     -   c. Alternatively, the constraint is updated to only impose         cross-layer alignment restrictions on the current layer and all         the lower layers that are the current layer's reference layer.     -   d. Alternatively, the constraint is updated to only impose         cross-layer alignment restrictions on the current layer and all         layers that are lower than the current layer.     -   e. Alternatively, the constraint is updated to only impose         cross-layer alignment restrictions on the current layer and all         the lower layers in each OLS containing the current layer.     -   f. Alternatively, the constraint is updated to only impose         cross-layer alignment restrictions on all layers that are lower         than the highest layer.     -   g. Alternatively, the constraint is updated to only impose         cross-layer alignment restrictions on all layers that are higher         than the lowest layer.         -   4) To solve problem 2, in one or more of the decoding             processes involving the clipping operations in the inter             prediction related processes for handling of subpicture             boundaries in motion compensation/motion prediction as             picture boundaries (e.g., in clauses 8.5.2.11 Derivation             process for temporal luma motion vector prediction,             8.5.3.2.2 Luma sample bilinear interpolation process,             8.5.5.3 Derivation process for subblock-based temporal             merging candidates, 8.5.5.4 Derivation process for             subblock-based temporal merging base motion data, 8.5.5.6             Derivation process for constructed affine control point             motion vector merging candidates, 8.5.6.3.2 Luma sample             interpolation filtering process, 8.5.6.3.3 Luma integer             sample fetching process, and 8.5.6.3.4 Chroma sample             interpolation process), the following changes are applied:     -   a. In one example, the processes are changed such that the         clipping operations are applied if         subpic_treated_as_pic_flag[CurrSubpicIdx] is equal to 1 and         sps_num_subpics_minus1 for the reference picture refPicLX is         greater than 0, and not applied otherwise.         -   i. Alternatively, when the collocated picture for a picture             is disallowed to be an ILRP, only the processes wherein the             reference picture refPicLX is not the collocated picture are             changed as described above, and the processes wherein the             reference picture refPicLX is the collocated picture is not             changed.     -   b. In one example, the processes are changed such that the         clipping operations are applied if         subpic_treated_as_pic_flag[CurrSubpicIdx] is equal to 1 and the         value of nal_unit_type of the current slice is not equal to         IDR_W_RADL, IDR_N_LP, or CRA_NUT, and not applied otherwise. At         the same time, ILP is allowed for coding of IRAP pictures only.     -   c. In one example, no changes to these decoding processes are         made, e.g., the clipping operations are applied if         subpic_treated_as_pic_flag[CurrSubpicIdx] is equal to 1 and not         applied otherwise, same as in the current VVC text. -   5) To solve problem 3a, the constraint on the combination of     subpictures and scalability with ILP is updated such that the     constraint imposes cross-layer alignment restrictions on all layers     in each dependency tree. A dependency tree contains a particular     layer, all layers that have the particular layer as a reference     layer, and all reference layers of the particular layer),     independent of whether any of the layers is an output layer of an     OLS. -   6) To solve problem 3b, the constraint on the combination of     subpictures and scalability with ILP is updated such that the     constraint imposes a cross-layer alignment restriction on the value     of subpic_treated_as_pic_flag[i]. -   7) To solve problem 3c, the constraint on the combination of     subpictures and scalability with ILP is updated such that the     constraint does not impose a cross-layer alignment restriction on     the value of loop_filter_across_subpic_enabled_flag[i]. -   8) To solve problem 3d, the constraint on the combination of     subpictures and scalability with ILP is updated such that the     constraint does not apply when sps_num_subpics_minus1 is equal to 0.     -   a. Alternatively, the constraint is updated such that the         constraint does not apply when subpic_info_present_flag is equal         to 0.         -   9) To solve problem 3e, the constraint on the combination of             subpictures and scalability with ILP is updated such that             the constraint imposes cross-layer alignment restrictions on             pictures in certain target set of AUs.     -   a. In one example, for each CLVS of a current layer referring to         the SPS, let the target set of AUs targetAuSet be all the AUs         starting from the AU containing the first picture of the CLVS in         decoding order, to the AU containing the last picture of the         CLVS in decoding order, inclusive. -   10) To solve problem 3f, the constraint on the combination of     subpictures and scalability with ILP is updated such that the     constraint imposes a cross-layer alignment restriction for the value     of each of the scaling window parameters scaling_win_left_offset,     scaling_win_right_offset, scaling_win_top_offset, and     scaling_win_bottom_offset. -   11) To solve problem 4, it is constrained that the collocated     picture for a current picture shall not be a long-term reference     picture (LTRP).     -   a. Alternatively, it is constrained that the collocated picture         for a current picture shall not be an inter-layer reference         picture (ILRP).     -   b. Alternatively, it is constrained that the collocated picture         for a current picture shall not be an LTRP or ILRP.     -   c. Alternatively, instead, if the collocated picture for a         current picture is an LTRP or ILRP, no scaling is applied to get         the motion vector pointing to the collocated picture. -   12) To solve problem 5, it is constrained that the value of each of     scaling_win_left_offset, scaling_win_right_offset,     scaling_win_top_offset, and scaling_win_bottom_offset shall be the     same for any two pictures within the same CLVS having the same     values of pic_width_in_luma_samples and pic_height_in_luma_samples,     respectively.     -   a. Alternatively, replace “within the same CLVS” above with         “within the same CVS”.     -   b. Alternatively, the constraint is specified as follows: Let         ppsA and ppsB be any two PPSs referring to the same SPS. It is a         requirement of bitstream conformance that, when ppsA and ppsB         have the same the values of pic width in luma samples and         pic_height_in_luma_samples, respectively, ppsA and ppsB shall         have the same values of scaling_win_left_offset,         scaling_win_right_offset, scaling_win_top_offset, and         scaling_win_bottom_offset, respectively.     -   c. Alternatively, the constraint is specified as follows: The         value of each of scaling_win_left_offset,         scaling_win_right_offset, scaling_win_top_offset, and         scaling_win_bottom_offset shall be the same for any two pictures         within the same CVS and satisfying all of the following         conditions:         -   i. The two pictures have the same values of             pic_width_in_luma_samples and pic_height_in_luma_samples,             respectively.         -   ii. The two pictures belong to the same layer or two layers             that one layer is a reference layer of the other layer. -   13) It is proposed that when the picture resolution/scaling window     is different for a current picture and other picture in the same     access unit, ILP is only allowed when the current picture is an IRAP     picture. -   14) In this document, the picture resolution may refer to the width     and/or height of a picture, or it may refer to the width and/or     height and/or top-left corner position of a scaling window/or     conformance window of the picture. -   15) In this document, RPR is not used may mean that the resolution     of any reference pictures of the current picture is the same to that     of the current picture. -   16) Regarding the bitstream extraction to solve problem 6, one or     more solutions are proposed as follows:     -   a. In one example, to derive the output sub-bitstream, remove         the parameter sets (e.g., SPS/PPS/APS NAL units) with         nuh_layer_id not included in the list         LayerIdInOls[targetOlsIdx].     -   b. For example, the derivation of the output sub-bitstream         OutBitstream may be dependent on one or more of the follows:         -   i. Remove from outBitstream all NAL units with nal_unit_type             equal to SPS_NUT and with nuh_layer_id not included in the             list LayerIdInOls[targetOlsIdx].         -   ii. Remove from outBitstream all NAL units with             nal_unit_type equal to PPS_NUT and with nuh_layer_id not             included in the list LayerIdInOls[targetOlsIdx].         -   iii. Remove from outBitstream all NAL units with             nal_unit_type equal to APS_NUT and with nuh_layer_id not             included in the list LayerIdInOls[targetOlsIdx].         -   iv. Remove from outBitstream all NAL units with             nal_unit_type equal to any of SPS_NUT , PPS_NUT, and APS_NUT             and any of the following conditions is true:             -   1. nuh_layer_id is greater than                 LayerIdInOls[targetOlsldx][j] for at least a value of j                 in the range of 0 to NumLayerslnOls[targetOlsIdx]—1                 inclusive.             -   2. nuh_layer_id not included in the list                 LayerIdInOls[targetOlsIdx].         -   v. When a first NAL unit with nal_unit_type equal to any of             SPS_NUT , PPS_NUT, and APS_NUT is removed during the             extraction, a second NAL unit referring to the first NAL             unit should also be removed.     -   c. For example, the derivation of the output sub-bitstream         OutBitstream may be dependent on one or more of the follows:         -   i. Remove from outBitstream all NAL units with nal_unit_type             equal to any of VPS_NUT, DCI_NUT, and EOB_NUT and with             nuh_layer_id not included in the list             LayerIdInOls[targetOlsIdx]. -   17) The bits required for signalling the APS ID (e.g.,     adaptation_parameter_set_id) is dependent on the APS type.     -   a. The bits required for signalling the APS ID (e.g.,         adaptation_parameter_set_id) is modified from u(3) to u(v).         -   i. In one example, for the adaptive loop filter (ALF) APS,             the APS ID may be coded with u(a).         -   ii. In one example, for the luma mapping with chroma scaling             (LMCS), the APS ID may be coded with u(b).         -   iii. In one example, for the Scaling list APSs, the APS ID             may be coded with u(c).         -   iv. In one example, the a/b/c is dependent on the maximum             allowed number of APSs for the corresponding type.             -   1. In one example, a>b and a>c.             -   2. In one example, a 22 =b and a 22 c.             -   3. In one example, c>b.             -   4. In one example, b 32 2.             -   5. In one example, c=3.             -   6. In one example, a=3 or greater than 3 (e.g., 4, 5, 6,                 7, 8, 9). -   18) The coding order of APS ID (e.g., adaptation_parameter_set_id)     and APS type (e.g., aps_params_type in the VVC text) is switched     that APS type is present before APS ID in the bitstream. -   19) The total number of allowed filters in APSs may be restricted     according to coded information, such as picture/slice types, coding     structure (dual tree or single tree), layer information.     -   a. The total number of allowed filters in APSs may include total         number of luma/chroma ALF and CC-ALF) in ALF APSs in all APS NAL         units with a PU.     -   b. The total number of allowed filters in APSs may include the         total number of adpative loop filter classes for luma component         (or luma ALF filters), the total number of alternative filters         for chroma components (chroma ALF filters), and/or the total         number of cross-component filters in all APS NAL units with a         PU. -   20) Regarding scaling factor larger than one to solve the eighth     problem, one or more solutions are proposed as follows:     -   a. In one example, the scaling windows offsets that are applied         to the picture size for scaling ratio calculation may be negtive         values.         -   i. For example, the syntax elements of scaling window             offsets (e.g., scaling_win_left_offset,             scaling_win_right_offset, scaling_win_top_offset,             scaling_win_bottom_offset) may be coded with signed             binarization, such as ae(v), f(n), i(n), se(v), and etc.     -   b. In one example, how to constrain the value of scaling window         offsets based on the picture size (e.g., picture width/height)         may be dependent on whether the value of a scaling windows         offset is negative or not.         -   i. For example, the constraints between offsets and picture             width/height may be diffirently specififed according to             whether the scaling window offset is negative or not.             -   1. For example, one or more constraints may be specified                 according to whether both the left and right offsets are                 negetive, and/or whether one of the left and right                 offsets is negative/prositive, and/or whether both the                 left and right offsets are positive.             -   2. For example, one or more constraints may be specified                 according to whether both the top and bottom offsets are                 negetive, and/or whether one of the top and bottom                 offsets is negative/prositive, and/or whether both the                 top and bottom offsets are positive.         -   ii. For example, only if the values of scaling window             offsets are positive value or 0, then the values of scaling             window offsets are restricted according to the picture             dimensions.             -   1. For example, when scaling_win_left_offset and                 scaling_win_right_offset are NOT negative (or, postive),                 then the value of                 SubWidthC*(scaling_win_left_offset+scaling_win_right_offset)                 shall be less than pic_width_in_luma_samples.             -   2. For example, when scaling_win_top_offset and                 scaling_win_bottom_offset are NOT negative (or,                 postive), then the value of                 SubHeightC*(scaling_win_top_offset+scaling_win_bottom_off                 set) shall be less than pic_height_in_luma_samples.         -   iii. For example, the absolute offset may be used to specify             the constraints.             -   1. For example, the value of                 SubWidthC*(abs(scaling_win_left_offset) 30                 abs(scaling_win_rig ht_offset)) shall be less than                 X1*pic_width_in_luma_samples, wherein in X1 is a posive                 integer such as X1>=1.             -   2. For example, the value of                 SubHeightC*(abs(scaling_win_top_offset)+abs(scaling_win_bottom_offset))                 shall be less than X2*pic_height_in_luma_samples,                 wherein in X2 is a posive integer such as X2>=1.         -   iv. Alternatively, when the value of any scaling window             offset is negative, don't constraint the offset value on the             picture width/height (e.g., treated the negative offset as             0-valued offset).             -   1. For example, the value of SubWidthC*(max(0,                 scaling_win_left_offset)+max(0,                 scaling_win_right_offset)) shall be less than                 pic_width_in_luma_samples.             -   2. For example, the value of SubHeightC*(max(0,                 scaling_win_top_offset) +max(0,                 scaling_win_bottom_offset)) shall be less than                 pic_height_in_luma_samples.     -   c. In one example, how to make bitstream conformance/constraints         among reference picture output width/height, current picture         output width/height, reference picture width/height, current         picture width/height, maximum picture width/height (e.g.,         refPicOutputWidthL, refPicOutputHeightL, PicOutputWidthL,         PicOutputHeightL, refPicWidthInLumaSamples,         refPicHeightInLumaSamples, pic_width/height_in_luma_samples,         pic_width/height_max_in_luma_samples) may be dependent on         whether the value of scaling windows offsets are negative or         not.     -   d. In one example, how to derive the width/height of the output         picture (e.g., PicOutputWidthL, PicOutputHeightL) may be         dependent on whether the value of a scaling windows offset is         negative or not.         -   i. For example, when the value of a scaling offset of a             reference picture is negative, it may be treated as 0-valued             offset for calculating the width/height of the output             picture for a reference picture.         -   ii. For example, the variable PicOutputWidthL may be derived             as follows:

PicOutputWidthL    =     pic_width_in_luma_samples − SubWidthC * (      max(0, scaling_win_right_offset) + max(0, scaling_win_left_offset) ).

-   -   -   iii. For example, the variable PicOutputHeightL may be             derived as follows:

PicOutputHeightL = pic_height_in_luma_samples −SubWidthC * ( max(0, scaling_win_bottom_offset) + max(0, scaling_win_top_offset) ).

-   -   e. In one example, how to perform the fractional sample         interpolation may be dependent on whether the value of a scaling         windows offset is negative or not.         -   i. For example, when the value of a scaling window offset of             a reference picture is negative, it may be treated as             0-valued offset for motion compensation.             -   1. For example, the variable fRefLeftOffset may be set                 equal to ((SubWidthC*max(0,                 scaling_win_left_offset))<<10), where                 scaling_win_left_offset is the scaling_win_left_offset                 for the reference picture.             -   2. For example, the variable fRefTopOffset may be set                 equal to ((SubWidthC*max(0, scaling_win_top_offset))                 <<10), where scaling_win_top_offset is the                 scaling_win_top_offset for the reference picture.         -   ii. For example, when the value of a scaling window offset             of a current picture is negative, it may be treated as             0-valued offset for fractional sample interpolation.             -   1. For example, let (refxSb_(L), refySbL) be luma                 locations pointed to by a motion vector (refMvLX[0],                 refMvLX[1]) given in 1/16-sample units. The variables                 refxSbL and refySb_(L) may be derived as follows:

a. refxSb_(L)   =   ( ( ( xSb − ( SubWidthC * max(0, scaling_win_left_offset )) )    <<    4 ) +  refMvLX[ 0 ] ) * scalingRatio[ 0 ] b. refySb_(L)   =   ( ( ( ySB − ( SubWidthC * max(0, scaling_win_top_offset )) )    < <   4 ) +  refMvLX[ 1 ] ) * scalingRatio[ 1 ]

-   -     2. For example, let (refxSbc, refySb_(c)) be chroma locations         pointed to by a motion vector (refMvLX[0], refMvLX[1]) given in         1/32-sample units. The variables refxSbc, and refySbc are         derived as follows:

a. refxSb_(C)   =    ( ( ( xSb − ( SubWidthC * max(0, scaling_win_left_offset) ) ) / SubWidthC << 5 ) + refMvLX[ 0 ] ) * scalingRatio[ 0 ] + addX b. refySb_(C)  =   ( ( ( ySb − ( SubWidthC * max(0, scaling_win_top_offset) ) ) / SubHeightC << 5 ) +  refMvLX[ 1 ] ) * scalingRatio[ 1 ] + addY

-   21)Regarding the signalling of TSRC/DQ/SHD to solve the ninth     problem, one or more solutions are proposed as follows:     -   a. In one example, the signalling of sign data hiding (SDH) and         dependent quantization (DQ) enable/disable flag in video unit         level (such as in sequence/group of pictures/picture/slice         level) may be dependent on whether the transform skip residual         coding (TSRC) is enabled.         -   i. For example, whether TSRC is enabled or not (e.g.,             sps/pps/ph/slice_ts_residual_coding_disabled_flag) may be             signalled before the enable/disable flag of SDH/DQ at the             same level (e.g., named             sps/pps/ph/slice_dep-quant_enabled_flag,             sps/pps/ph/slice_sign_data_hiding_enabled_flag).         -   ii. For example, the signalling of SDH/DQ enable/disable             flag in SPS/PPS/PH/SH level (e.g., named             sps/pps/ph/slice_dep_quant_enabled_flag,             sps/pps/ph/slice_sign_data_hiding_enabled_flag) may be             conditioned on whether TSRC is disabled at the same level or             higher level (e.g., whether             sps/pps/ph/slice_ts_residual_coding_disabled_flag is equal             to 1).         -   iii. For example, the syntax signalling in the SH (on top of             JVET-Q2001-vE) may be changed as follows:

Descriptor slice_header( ) { ... slice_ts_residual_coding_disabled_flag u(1)  

  

   

   

   

   

  

   

  

   

  

   

   

  ...

-   -   -   iv. Additionally, infer             sps/pps/ph/slice_dep_quant_enabled_flag to be equal to a             certain value (such as 0) when not present.         -   v. Additionally, infer             sps/pps/ph/slice_sign_data_hiding_enabled_flag to be equal             to a certain value (such as 0) when not present.

    -   b. In one example, whether TSRC is enabled or not may be         signalled in a video unit level (such as in sequence/ group of         pictures/picture/slice level).         -   i. For example, a flag named as             (sps/pps/ph/slice)_ts_residual_coding_enabled_flag may be             signalled in the SPS/PPS/PH/SH.         -   ii. Alternatively, whether TSRC is disabled or not may be             signalled in a video unit level (such as in sequence/group             of pictures/picture/slice level).         -   iii. For example, a flag named as             (sps/pps/ph/slice)_ts_residual_coding_disabled_flag may be             signalled in the SPS/PPS/PH/SH.

    -   c. In one example, whether TSRC is enabled or not is         conditionally signalled, based on whether transform skip and DQ         and SDH enabled or not at the same level or the higher level.         -   i. For example, slice_ts_residual_coding_disabled_flag is             conditionally signalled, based on             (sps_transform_skip_enabled_flag=1 && !             slice_dep_quant_enabled_flag &&!             slice_sign_data_hiding_enabled_flag).         -   ii. For example, ph_ts_residual_coding_disabled_flag is             conditionally signalled, based on             (sps_transform_skip_enabled_flag=1 && !             ph_dep_quant_enabled_flag &&!             ph_sign_data_hiding_enabled_flag).         -   iii. For example, pps_ts_residual_coding_disabled_flag is             conditionally signalled, based on             (sps_transform_skip_enabled_flag=1 && !             pps_dep_quant_enabled_flag &&!             pps_sign_data_hiding_enabled_flag).         -   iv. In above example, sps_transform_skip_enabled_flag may be             replaced by SPS TSRC enabled flag/SPS TSRC disabled flag.         -   v. in above example, sps_transform_skip_enabled_flag may be             replaced by PPS TS enabled flag/PPS TSRC enabled flag/PPS             TSRC disabled flag.

    -   d. In one example, whether to apply SDH or DQ in a block may         depend whether TS and/or TSRS is used.

    -   e. In one example, when TS and/or TSRS is used in a block, SDH         and/or DQ is not applied. ii. In one example, the SE(s)         indicating whether SDH and/or DQ is used are not signaled and         inferred to be not used when TS and/or TSRS is used in a block.

    -   f. In one example, it is constrained that SDH and/or DQ cannot         be used if TS and/or TSRS is used in a block.

-   22) It may be required that a scaling widow offset (such as     scaling_win_right_offset, scaling_win_left_offset,     scaling_win_top_offset, scaling_win_bottom_offset) shall be greater     than (or no smaller than) an integer X, wherein X is negtive.     -   a. In one example, X may be dependent on picture dimensions.

-   23) The variables PicOutputWidthL and PicOutputHeightL are derived     as follows:

PicOutputWidthL = pic_width_in_luma_ samples −SubWidthC * ( scaling_win_right_offset + scaling_win_left_offset ) PicOutputHeightL = pic_height_in_luma_samples −SubWidthC * ( scaling_win_bottom_offset + scaling_win_top_offset).

Then one or more of the following restrictions may be applied:

a. ((aX1 * PicOutputWidthL +bX1)>>cX1) <= ((dX1*X1 +eX1)>>fX1) wherein X1 is a non-negtive integer. b. ((aX0 * PicOutputWidthL +bX0)>>cX0) >= ((dX0*X1 +eX0)>>fX0), wherein X0 is a non-negtive integer. c. ((aY1 * PicOutputHeightL+bY1)>>cY1) <= (dY1*Y1+eY1)>>fY1, wherein Y1 is a non-negtive integer. d. ((aY0 * PicOutputHeightL+bY0)>>cY0) <= (dY0*Y0+eY0)>>fY0, wherein Y0 is a non-negtive integer. e. ((aXY1 * PicOutputWidthL * PicOutputHeightL+bXY1)>>cXY1) <= (dXY1*XY1+eXY1)>>fXY1, wherein XY1 is a non-negtive integer. f. ((aXY0 * PicOutputWidthL * PicOutputHeightL+bXY0)>>cXY0) <= (dXY0*Y0+eXY0)>>fXY0, wherein XY0 is a non-negtive integer.

-   -   g. In the above restrictions, aX1, bX1, . . . eX1, fX1, aXO,         bXO, . . . eXO, fXO, aY1, bY1, . . . eY1, fY1, aYO, bYO, . . .         eYO, fYO, aXY1, bXY1, . . . eXY1, fXY1, aXYO, bXYO, . . . eXYO,         fXYO, are integers. In one example, aX1=aX0=aY1=aY0=aXY1=aXYO=1,         bX1=bX0=bY1=bY0=bXY1=bXYO=0, cX1=cX0=cY1=cY0=cXY1=cXY0=0,         dX1=dX0=dY1=dY0 =dXY=dXY0=1, eX1=eX0=eY1=eY0=eXY1=eXY0=0,         fX1=fX0=fY1=fY0=fXY1=fXY0=0,     -   h. In the above restrictions, X1 and/or X0 may depend on         pic_width_in_luma_samples.         -   i. In one example, X1 is equal to pic_width_in_luma_samples         -   ii. In one example, PicOutputWidthL<=pic_width_in_luma             samples*K, wherein K is a positive integer such as 2, 3, 4,             5, 6, 7, 8.     -   i. In the above restrictions, Y1 and/or Y0 may depend on         pic_height_in_luma_samples.         -   i. In one example, Y1 is equal to pic_height_in_luma_samples         -   ii. In one example,             PicOutputHeightL<=pic_height_in_luma_samples*K, wherein K is             a positive integer such as 2, 3, 4, 5, 6, 7, 8.

-   24) In one example, the maximum allowed value of     five_minus_max_num_subblock_merge_cand may be equal to X wherein X     is smaller than 5. E.g. X=4.     -   a. For example, five_minus_max_num_subblock_merge_cand specifies         the maximum number of subblock-based merging motion vector         prediction candidates supported in the SPS subtracted from 5.         The value of five_minus_max_num_subblock_merge_cand shall be in         the range of 0 to 4, inclusive. When not present, the value of         five_minus_max_num_subblock_merge_cand is inferred to be equal         to 5.

-   25) How to define the valid range of     five_minus_max_num_subblock_merge_cand may depend on whether     five_minus_max_num_subblock_merge is present or not.     -   a. For example, a valid range of five_minus_max_num_subblock         merge is defined only when five_minus_max_num_subblock_merge is         present.     -   b. For example, different valid ranges of         five_minus_max_num_subblock_merge are defined depending on         five_minus_max_num_subblock_merge is present or not.     -   c. For example, five_minus_max_num_subblock_merge_cand specifies         the maximum number of subblock-based merging motion vector         prediction candidates supported in the SPS subtracted from 5.         The value of five_minus_max_num_subblock_merge_cand shall be in         the range of 0 to 5—sps_sbtmvp_enabled_flag, inclusive when         five_minus_max_num_subblock_merge_cand is present. When not         present, the value of five_minus_max_num_subblock_merge cand is         inferred to be equal to 5.     -   d. For example, five_minus_max_num_subblock_merge_cand specifies         the maximum number of subblock-based merging motion vector         prediction candidates supported in the SPS subtracted from         5.When not present, the value of         five_minus_max_num_subblock_merge_cand is inferred to be equal         to 5. Otherwise (five_minus_max_num_subblock_merge cand is         present), the value of five_minus_max_num_subblock_merge_cand         shall be in the range of 0 to 5—sps sbtmvp enabled flag,         inclusive. For example, five_minus_max_num_subblock_merge_cand         specifies the maximum number of subblock-based merging motion         vector prediction candidates supported in the SPS subtracted         from 5. The value of five_minus_max_num_subblock_merge_cand         shall be in the range of 0 to 5 — sps affine enabled flag,         inclusive when five_minus_max_num_subblock_merge_cand is         present. When not present, the value of         five_minus_max_num_subblock_merge cand is inferred to be equal         to 5.     -   e. For example, five_minus_max_num_subblock_merge_cand specifies         the maximum number of subblock-based merging motion vector         prediction candidates supported in the SPS subtracted from         5.When not present, the value of         five_minus_max_num_subblock_merge_cand is inferred to be equal         to 5. Otherwise (five_minus_max_num_subblock_merge cand is         present), the value of five_minus_max_num_subblock_merge_cand         shall be in the range of 0 to 5—sps affine enabled flag,         inclusive.     -   f. For example, five_minus_max_num_subblock_merge_cand specifies         the maximum number of subblock-based merging motion vector         prediction candidates supported in the SPS subtracted from 5.         The value of five_minus_max_num_subblock_merge_cand shall be in         the range of 0 to 4, inclusive when         five_minus_max_num_subblock_merge cand is present. When not         present, the value of five_minus_max_num_subblock_merge cand is         inferred to be equal to 5.     -   g. For example, five_minus_max_num_subblock_merge_cand specifies         the maximum number of subblock-based merging motion vector         prediction candidates supported in the SPS subtracted from         5.When not present, the value of         five_minus_max_num_subblock_merge_cand is inferred to be equal         to 5. Otherwise (five_minus_max_num_subblock_merge cand is         present), the value of five_minus_max_num_subblock_merge_cand         shall be in the range of 0 to 4, inclusive.

-   26) Regarding the CTU size of the collocated picture to solve the     tenth problem, one or more solutions are proposed as follows:     -   a. In one example, when the CTU/CTB size of the collocated         reference picture is greater than (or less than, or not equal         to) the CTU/CTB size of the current picture, it is required that         any coding tool that uses motion information from a different         picture (e.g., TMVP, and/or SbTMVP) shall be disallowed/disabled         to the current slice/tile/tile groups/subpicture/picture/a video         unit smaller than the current picture.     -   b. In one example, when an inter-layer reference picture has         CTU/CTB size greater than (or less than, or not equal to) the         CTU/CTB size of the current picture, it is required that any         coding tool that uses motion information from a different         picture (e.g., TMVP, and/or SbTMVP) shall be disallowed/disabled         to the current slice/tile/tile groups/subpicture/picture/video         unit.     -   c. In above examples, when any coding tool that uses motion         information from a different picture is disallowed/disabled,         indication of usage of TMVP/SbTMVP is required to be equal to 0.         -   i. In one example, ph_temporal_mvp_enabled_flag shall be             equal to 0.     -   d. In one example, whether to signal or how to signal the         enabling of a coding tool that uses motion information from a         different picture (e.g., TMVP, and/or SbTMVP) may depend on the         CTU sizes of reference pictures in the reference picture lists         of current video unit (e.g., slice/picture).         -   i. In one example, if all reference pictures are with             different CTU sizes (e.g., smaller or greater) as that of             the current video unit, a conformance bitstream shall             satisfy that the usage of temporal motion vector prediction             is disabled.         -   ii. In one example, if all reference pictures are with             different CTU sizes (e.g., smaller or greater) as that of             the current video unit, the indication of usage of temporal             motion vector prediction (e.g.,             ph_temporal_mvp_enabled_flag) is not signalled.             -   1. Alternatively, furthermore, it is inferred to be                 disabled.             -   2. Alternatively, furthermore, the indications of                 collocated reference pictures (e.g.,                 sh_collocated_from_10_flag, sh_collocated_ref_idx,                 ph_collocated_from_10_flag, ph_collocated_ref_idx) are                 not signalled any more.     -   e. In one example, any reference picture, with CTU/CTB size         greater than (or less than, or not equal to) the CTU/CTB size of         the current picture, is not allowed to be a collocated picture         of the current slice/tile/tile groups/subpicture/picture/video         unit.     -   f. In one example, any picture, with CTU/CTB size greater than         (or less than, or not equal to) the CTU/CTB size of the current         picture, is not allowed to be marked as a collocated picture of         the current slice/tile/tile groups/subpicture/picture/video         unit.     -   g. In one example, for the collocated picture to be utilized for         current picture/slice/tile/brick/subpicture/a video unit smaller         than a picture, it is required that the CTU/CTB size of the         collocated picture shall be equal to the size of CTU/CTB of the         current picture/slice/tile/brick/subpicture/a video unit smaller         than a picture.         -   i. In one example, the reference picture is identified by             the sh_collocated_from_10_flag and/or sh_collocated_ref_idx.         -   ii. In one example, the reference picture is identified by             the ph_collocated_from_10_flag and/or ph_collocated_ref_idx.     -   h. In one example, the above collocated picture indicates the         collocated picture used for temporal motion vector prediction.     -   i. In one example, the above CTU/CTB size may be identified by         the SPS syntax element specifying the CTU size (e.g.,         sps_log2_ctu_size_minus5).     -   j. The above requirement may be represented as a bitstream         constraint/conformance.

6. Embodiments

Below are some example embodiments for some of the invention aspects summarized above in Section 5, which can be applied to the VVC specification. Most relevant parts that have been added or modified are underlined in

and some of the deleted parts are indicated using [[ ]].

6.1. First Embodiment

This embodiment is for items 1, 1.a, 1.b, 1.c, 1.d, 3, 4.a.i, 5, 6, 7, 8, 9, 9.a, 10, 11, and 12b.

7.3.2.3 Sequence Parameter Set Syntax

Descriptor seq_parameter_set_rbsp( ) {  ...  

   

   

  

    res_change_in_clvs_allowed_flag u(1)  pic_width_max_in_luma_samples ue(v)  pic_height_max_in_luma_samples ue(v)  ... } 7.4.3.3 Sequence Parameter Set RBSP Semantics

res_change_in_clvs_allowed_flag equal to 1 specifies that the picture spatial resolution may change within a CLVS referring to the SPS. res_change_in_clvs_allowed_flag equal to 0 specifies that the picture spatial resolution does not change within any CLVS referring to the SPS.

subpic_treated_as_pic_flag[i] equal to 1 specifies that the i-th subpicture of each coded picture in the CLVS is treated as a picture in the decoding process excluding in-loop filtering operations. subpic_treated_as_pic_flag[i] equal to 0 specifies that the i-th subpicture of each coded picture in the CLVS is not treated as a picture in the decoding process excluding in-loop filtering operations. When not present, the value of subpic_treated_aspic_flag[i] is inferred to be equal to sps_independent_subpics_flag.

When

subpic_treated_as_pic_flag[i] is equal to 1,

-   All pictures     shall have the same value of pic_width_in_luma_samples and the same     value of pic_height_in_luma_samples.

-   

-   All the SPSs referred to by     shall have the same value of sps_num_subpics_minus1 and shall have     the same values of subpic_ctu_top_left_x[j],     subpic_ctu_top_left_y[j], subpic_width_minus 1 [j],     subpic_height_minus 1 [j], and     [loop_filter_across_subpic_enabled_flag [j], ]] respectively, for     each value of j in the range of 0 to sps_num_subpics_minus1,     inclusive.

-   All pictures     shall have the same value of SubpicIdVa1[j] for each value of j in     the range of 0 to sps_num_subpics_minus1, inclusive.

7.4.3.4 Picture Parameter Set RBSP Semantics

scaling_window_explicit_signalling_flag equal to 1 specifies that the scaling window offset parameters are present in the PPS. scaling_window_explicit_signalling_flag equal to 0 specifies that the scaling window offset parameters are not present in the PPS. When

res change_in_clvs_allowed_flag]] is equal to 0, the value of scaling_window_explicit_signalling_flag shall be equal to 0. scaling_win_left_offset, scaling_win_right_offset, scaling_win_top_offset, and scaling_win_bottom_offset specify the offsets that are applied to the picture size for scaling ratio calculation. When not present, the values of scaling_win_left_offset, scaling_win_right_offset, scaling_win_top_offset, and scaling_win_bottom_offset are inferred to be equal to pps_conf_win_left_offset, pps_conf_win_right_offset, pps_conf_win_top_offset, and pps_conf_win_bottom_offset, respectively. The value of SubWidthC*(scaling_win_left_offset+scaling_win_right_offset) shall be less than pic_width_in_luma_samples, and the value of SubHeightC*(scaling_win_top_offset 30 scaling_win_bottom_offset) shall be less than pic_height_in_luma_samples.

The variables PicOutputWidthL and PicOutputHeightL are derived as follows:

PicOutputWidthL = pic_width_in_luma_samples − (78)  SubWidthC * ( scaling_win_right_offset +  scaling_win_left_offset ) PicOutputHeightL = pic_height_in_luma_samples − (79)  SubWidthC * ( scaling_win_bottom_offset +  scaling_win_top_offset ) Let refPicOutputWidthL and refPicOutputHeightL be the PicOutputWidthL and PicOutputHeightL, respectively, of a reference picture of a current picture referring to this PPS. It is a requirement of bitstream conformance that all of the following conditions are satisfied:

- PicOutputWidthL * 2 shall be greater than or equal to refPicWidthInLumaSamples. - PicOutputHeightL * 2 shall be greater than or equal to refPicHeightInLumaSamples. - PicOutputWidthL shall be less than or equal to refPicWidthInLumaSamples * 8. - PicOutputHeightL shall be less than or equal to refPicHeightInLumaSamples * 8. - PicOutputWidthL * pic_width_max_in_luma_samples shall be greater than or equal to refPicOutputWidthL * (pic_width_in_luma_samples − Max( 8, MinCbSizeY )). - PicOutputHeightL * pic_height_max_in_luma_samples shall begreater than or equal to refPicOutputHeightL * (pic_height_in_luma_samples − Max( 8, MinCbSizeY )).

7.3.3.2 General Constraint Information Syntax

Descriptor general_constraint_info( ) {  ...  

  

   

   no_res_change_in_clvs_constraint_flag u(1)  ... } 7.4.4.2 General Constraint Information Semantics

no_res_change_in_clvs_constraint_flag equal to 1 specifies that res_change_in_clvs_allowed_flag shall be equal to 0. no_res_change_in_clvs_constraint_flag equal to 0 does not impose such a constraint.

7.4.8.1 General Slice Header Semantics

slice_collocated_from_10_flag equal to 1 specifies that the collocated picture used for temporal motion vector prediction is derived from reference picture list 0. slice_collocated_from_10_flag equal to 0 specifies that the collocated picture used for temporal motion vector prediction is derived from reference picture list 1. When slice_type is equal to B or P, ph_temporal_mvp_enabled_flag is equal to 1, and slice_collocated_from_10_flag is not present, the following applies:

-   If rpl_nfo_in_ph_flag is equal to 1, slice_collocated_from_10_flag     is inferred to be equal to ph_collocated_from_10_flag. -   Otherwise (rpl_info_in_ph_flag is equal to 0 and slice_type is equal     to P), the value of slice_collocated_from_10_flag is inferred to be     equal to 1.     slice_collocated_ref_idx specifies the reference index of the     collocated picture used for temporal motion vector prediction.     When slice_type is equal to P or when slice_type is equal to B and     slice_collocated_from_10_flag is equal to 1,     slice_collocated_ref_idx refers to an entry in reference picture     list 0, and the value of slice_collocated_ref_idx shall be in the     range of 0 to NumRefldxActive[0]— 1, inclusive. When slice_type is     equal to B and slice_collocated_from_10_flag is equal to 0,     slice_collocated_ref_idx refers to an entry in reference picture     list 1, and the value of slice_collocated_ref_idx shall be in the     range of 0 to NumRefIdxActive[1]—1, inclusive.     When slice_collocated_ref_idx is not present, the following applies: -   If rpl_info_in_ph_flag is equal to 1, the value of     slice_collocated_ref_idx is inferred to be equal to     ph_collocated_ref_idx. -   Otherwise (rpl_info_in_ph_flag is equal to 0), the value of     slice_collocated_ref_idx is inferred to be equal to 0.     It is a requirement of bitstream conformance that the picture     referred to by slice_collocated_ref_idx shall be the same for all     slices of a coded picture     It is a requirement of bitstream conformance that the values of     pic_width_in_luma_samples and pic_height_in_luma_samples of the     reference picture referred to by slice_collocated_ref_idx shall be     equal to the values of pic_width_in_luma_samples and     pic_height_in_luma_samples, respectively, of the current picture,     and RprConstraintsActive[slice_collocated_from_10_flag     ?0:1][slice_collocated_ref_idx] shall be equal to 0.

8.5.3.2.2 Luma Sample Bilinear Interpolation Process

The luma locations in full-sample units (xInt_(i), yInt_(i)) are derived as follows for i=0..1:

-   If subpic_treated_as_pic_flag[CurrSubpicIdx] is equal to 1     the following applies:

xInt_(i) = Clip3( SubpicLeftBoundaryPos, SubpicRightBoundaryPos, (640) xInt_(L) + i ) yInt_(i) = Clip3( SubpicTopBoundaryPos, SubpicBotBoundaryPos, (641) yInt_(L) + i )

-   Otherwise (subpic_treated_as_pic_flag[CurrSubpicldx] is equal to 0     the following applies:

 xInt_(i) = Clip3( 0, picW − 1, refWraparoundEnabledFlag ?   ClipH( ( PpsRefWraparoundOffset ) * MinCbSizeY, (642)     picW, (xInt_(L) + i ) ) : xInt_(L) + i )  yInt_(i) = Clip3( 0, picH − 1, yInt_(L) + i ) (643) ...

8.5.6.3.2 Luma Sample Interpolation Filtering Process

-   If subpic_treated_as_pic_flag[CurrSubpicldx] is equal to 1     the following applies:

xInt_(i) = Clip3( SubpicLeftBoundaryPos, SubpicRightBoundaryPos, (959) xInt_(i) ) yInt_(i) = Clip3( SubpicTopBoundaryPos, SubpicBotBoundaryPos, (960) yInt_(i) ) Otherwise (subpic_treated_as_pic_flag [CurrSubpicldx] is equal to 0

the following applies:

 xInt_(i) = Clip3( 0, picW − 1, refWraparoundEnabledFlag ?   ClipH( ( PpsRefWraparoundOffset ) * MinCbSizeY, picW, (961)    xInt_(i) ) : xInt_(i) )  yInt_(i) = Clip3( 0, picH − 1, yInt_(i) ) (962) ...

8.5.6.3.3 Luma Integer Sample Fetching Process

The luma locations in full-sample units (xInt, yInt) are derived as follows:

-   If subpic_treated_as_pic_flag [CurrSubpicldx] is equal to 1     the following applies:

xInt = Clip3( SubpicLeftBoundaryPos, SubpicRightBoundaryPos, (968) xInt_(L) ) yInt = Clip3( SubpicTopBoundaryPos, SubpicBotBoundaryPos, (969) yInt_(L) )

-   Otherwise     the following applies:

 xInt = Clip3( 0, picW − 1, refWraparoundEnabledFlag ? (970)   ClipH( ( PpsRefWraparoundOffset ) * MinCbSizeY, picW,   xInt_(L) ) : xInt_(L) )  yInt = Clip3( 0, picH − 1, yInt_(L) ) (971) ...

8.5.6.3.4 Chroma Sample Interpolation Process

-   If subpic_treated_as_pic_flag [CurrSubpicldx] is equal to 1     the following applies:

xInt_(i) = Clip3( SubpicLeftBoundaryPos / SubWidthC, (977) SubpicRightBoundaryPos / SubWidthC, xInt_(i) ) yInt_(i) = Clip3( SubpicTopBoundaryPos / SubHeightC, (978) SubpicBotBoundaryPos / SubHeightC, yInt_(i) )

-   Otherwise (subpic_treated_aspic_flag [CurrSubpicldx] is equal to 0     the following applies:

 xInt_(i) = Clip3( 0, picW_(C) − 1, refWraparoundEnabledFlag ? (979)   ClipH( xOffset, picW_(C), xInt_(i) ) : xInt_(C) + i − 1 )  yInt_(i) = Clip3( 0, picH_(C) − 1, yInt_(i) ) (980) ... Alternatively, the highlighted part “and sps_num_subpics_minus1 for the reference picture refPicLX is greater than 0” may be replaced by “and if the reference picture refPicLX is an ILRP having a same spatial resolution with the current picture”. Alternatively, the highlighted part “or sps_num_subpics_minus1 for the reference picture refPicLX is equal to 0” may be replaced by “or if the reference picture refPicLX is an ILRP having a different spatial resolution than the current picture”. Alternatively, the requirement for collocated picture, e.g., “It is a requirement of bitstream conformance that the picture referred to by slice_collocated_ref_idx shall be the same for all slices of a coded picture

may be replaced by “It is a requirement of bitstream conformance that the picture referred to by slice_collocated_ref_idx shall be the same for all slices of a coded picture

Alternatively, the requirement for collocated picture, e.g., “It is a requirement of bitstream conformance that the picture referred to by slice_collocated_ref_idx shall be the same for all slices of a coded picture

may be replaced by “It is a requirement of bitstream conformance that the picture referred to by slice_collocated_ref_idx shall be the same for all slices of a coded picture

6.2. Second Embodiment

In some alternative embodiments, the following constraint in the first embodiment:

-   -   When         subpic_treated_as_pic_flag[i] is equal to 1,         it is a requirement of bitstream conformance that all of the         following conditions are true for

    -   All pictures         shall have the same value of pic_width_in_luma_samples and the         same value of pic_height_in_luma_samples.

    -   

    -   All the SPSs referred to by         shall have the same value of sps_num_subpics_minus1 and shall         have the same values of subpic_ctu_top_left_x[j],         subpic_ctu_top_left_y[j], subpic_width_minus1[j],         subpic_height_minus1 [j], and         [[loop_filter_across_subpic_enabled_flag[j], ]]respectively, for         each value of j in the range of 0 to sps_num_subpics_minus1,         inclusive.

    -   All pictures of         shall have the same value of

SubpicIdVal [j] for each value of j in the range of 0 to sps_num_subpics_minus1, inclusive. is replaced with one of the following:

1) When

subpic_treated_as_pic_flag[i] is equal to 1,

it is a requirement of bitstream conformance that all of the following conditions are true for

-   -   All pictures         shall have the same value of pic_width_in_luma_samples and the         same value of pic_height_in_luma_samples.

    -   

    -   All the SPSs referred to         shall have the same value of sps_num_subpics_minus1 and shall         have the same values of subpic_ctu_top_left_x[j],         subpic_ctu_top_left_y[j], subpic_width_minus1 [j],         subpic_height_minus1 [j], [[and         loop_filter_across_subpic_enabled_flag[j], ]] respectively, for         each value of j in the range of 0 to sps_num_subpics_minus1,         inclusive.

    -   All pictures         shall have the same value of SubpicIdVal[j] for each value of j         in the range of 0 to sps_num_subpics_minus1, inclusive.

2) When sps_num_subpics_minus1 is greater than 0 and subpic_treated_as_pic_flag[i] is equal to 1,

it is a requirement of bitstream conformance that all of the following conditions are true

-   -   All pictures         shall have the same value of pic_widthin_luma_samples and the         same value of pic_height_in_luma_samples.

    -   

    -   All the SPSs referred to by         shall have the same value of sps_num_subpics_minus1 and shall         have the same values of subpic_ctu_top_left_x[j],         subpic_ctu_top_left_y[j], subpic_width_minus1 [j],         subpic_height_minus1 [j], and         loop_filter_across_subpic_enabled_flag[j], respectively, for         each value of j in the range of 0 to sps_num_subpics_minus1,         inclusive.

    -   All pictures         have the same value of SubpicIdVal[j] for each value of j in the         range of 0 to sps_num_subpics_minus1, inclusive.

3) When subpic_treated_as_pic_flag[i] is equal to 1,

it is a requirement of bitstream conformance that all of the following conditions are true for

-   -   All pictures         shall have the same value of pic_width_in_luma_samples and the         same value of pic_height_in_luma_samples.

    -   

    -   All the SPSs referred to by         shall have the same value of sps_num_subpics_minus1 and shall         have the same values of subpic_ctu_top_left_x[j],         subpic_ctu_top_left_y[j], subpic_width_minus1 [j],         subpic_height_minus1 [j], and         [[loop_filter_across_subpic_enabled_flag j], ]] respectively,         for each value of j in the range of 0 to sps_num_subpics_minus1,         inclusive.

    -   All pictures         shall have the same value of SubpicIdVal[j] for each value of j         in the range of 0 to sps_num_subpics_minus1, inclusive.

4) When

subpic_treated_as_pic_flag[i] is equal to 1,

it is a requirement of bitstream conformance that all of the following conditions are true for

-   -   All pictures         shall have the same value of pic_widthin_lumasamples and the         same value of pic_height_in_lumasamples.

    -   

    -   All the SPSs referred to by         shall have the same value of sps_num_subpics_minus1 and shall         have the same values of subpic_ctu_top_left_x[j],         subpic_ctu_top_left_y[j], subpic_width_minus1 [j],         subpic_height_minus1 [j],         and loop_filter_across_subpic_enabled_flag[j], respectively, for         each value of j in the range of 0 to sps_num_subpics_minus1,         inclusive.

    -   All pictures         shall have the same value of SubpicIdVal[j] for each value of j         in the range of 0 to sps_num_subpics_minus1, inclusive.

6.3. Third Embodiment

This example proposes the following aspects regarding restrictions of the maximum numbers of ALF and CC-ALF filters:

1) Replace the constraints on the number of ALF APSs with constraints on the number of filters, more specifically, the following constrain are proposed to be added:

The total number of adpative loop filter classes for luma component, the total number of alternative filters for chroma components, and the total number of cross-component filters in all APS NAL units for a PU shall be less than or equal to 200, 64, and 64, respectively.

2) On top of item 1), further change the coding of the APS ID in the APS syntax from u(5) to u(v), with the length being 9, 2, and 3, respectively for ALF, LMCS, and scaling list APSs, respectively.

3) On top of item 1), further change the coding of ALF APS indices and the number of ALF APSs in PH and SH from u(v) to ue(v).

7.3.2.5 Adaptation Parameter Set RBSP Syntax

Descriptor adaptation_parameter_set_rbsp( ) {  [[adaptation_parameter_set_id u(5)]]  aps_params_type u(3)  

   

   if( aps_params_type = = ALF_APS )   alf_data( )  else if( aps_params_type = = LMCS_APS )   lmcs_data( )  else if( aps_params_type = = SCALING_APS )   scaling_list_data( )  aps_extension_flag u(1)  if( aps_extension_flag )   while( more_rbsp_data( ))    aps_extension_data_flag u(1)  rbsp_trailing_bits( ) }

7.3.2.7Picture Header Structure Syntax

Descriptor picture_header_structure( ) { ...  if( sps_alf_enabled_flag && alf_info_in_ph_  flag ) {   ph_alf_enabled_flag u(1)   if( ph_alf_enabled_flag ) {    ph_num_alf_aps_ids_luma u 

 [[3]])    for( i = 0; i < ph_num_alf_aps_ids_luma;    i++ )     ph_alf_aps_id_luma[ i ] u 

 [[3]])    if( ChromaArrayType != 0 )     ph_alf_chroma_idc u(2)    if( ph_alf_chroma_idc > 0 )     ph_alf_aps_id_chroma u 

 [[3]])    if( sps_ccalf_enabled_flag ) {     ph_cc_alf_cb_enabled_flag u(1)     if( ph_cc_alf_cb_enabled_flag )      ph_cc_alf_cb_aps_id u 

 [[3]])     ph_cc_alf_cr_enabled_flag u(1)     if( ph_cc_alf_cr_enabled_flag )      ph_cc_alf_cr_aps_id u 

 [[3]])    }   }  } ...

7.3.7.1General Slice Header Syntax

Descriptor slice_header( ) { ...  if( sps_alf_enabled_flag && !alf_info_in_ph_flag ) {   slice_alf_enabled_flag u(1)   if( slice_alf_enabled_flag ) {    slice_num_alf_aps_ids_luma u 

 [[3]]))    for( i = 0; i < slice_num_alf_aps_ids_luma;    i++ )     slice_alf_aps_id_luma[ i ] u 

 [[3]]))    if( ChromaArrayType != 0 )     slice_alf_chroma_idc u(2)    if( slice_alf_chroma_idc )     slice_alf_aps_id_chroma u 

 [[3]]))    if( sps_cc_alf_enabled_flag ) {     slice_cc_alf_cb_enabled_flag u(1)     if( slice_cc_alf_cb_enabled_flag )      slice_cc_alf_cb_aps_id u 

 [[3]]))     slice_cc_alf_cr_enabled_flag u(1)     if( slice_cc_alf_cr_enabled_flag )      slice_cc_alf_cr_aps_id u 

 [[3]]))    }   }  } ...

7.4.3.5 Adaptation Parameter Set Semantics

Each APS RBSP shall be available to the decoding process prior to it being referenced, included in at least one AU with TemporalId less than or equal to the TemporalId of the coded slice NAL unit that refers it or provided through external means. All APS NAL units with a particular value of adaptation_parameter_set_id and a particular value of aps_params_type within a PU, regardless of whether they are prefix or suffix APS NAL units, shall have the same content. adaptation_parameter_set_id provides an identifier for the APS for reference by other syntax elements. The length of the syntax element adaptation_parameter_set_id, in bits, is aps_params_type =ALF_APS ? 9:(aps_params_type==LMCS_APS ? 2:3). When aps_params_type is equal to ALF_APS [[or SCALING_APS]], the value of adaptation_parameter_set_id shall be in the range of 0 to [[7]]

, inclusive. [[When aps_params_type is equal to LMCS_APS, the value of adaptation_parameter_set_id shall be in the range of 0 to 3, inclusive.]] Let apsLayerId be the value of the nuh_layer_id of a particular APS NAL unit, and vclLayerId be the value of the nuhlayer_id of a particular VCL NAL unit. The particular VCL NAL unit shall not refer to the particular APS NAL unit unless apsLayerld is less than or equal to vclLayerld and the layer with nuh_layer_id equal to apsLayerld is included in at least one OLS that includes the layer with nuh_layer_id equal to vclLayerld. aps_params_type specifies the type of APS parameters carried in the APS as specified in Table 6.

All APS NAL units with a particular value of aps_params_type, regardless of the nuh_layer_id values, share the same value space for adaptation_parameter_set_id. APS NAL units with different values of aps_params_type use separate values spaces for adaptation_parameter_set_id.

7.4.3.7Picture Header Structure Semantics

ph_num_alf_aps_ids_luma specifies the number of ALF APSs that the slices associated with the PH refers to.

ph_alf_aps_id_luma[i] specifies the adaptation_parameter_set_id of the i-th ALF APS that the luma component of the slices associated with the PH refers to.

ph_alf_aps_id_chroma specifies the adaptation_parameter_set_id of the ALF APS that the chroma component of the slices associated with the PH refers to.

ph_cc_alf_cb_aps_id specifies the adaptation_parameter_set_id of the ALF APS that the Cb colour component of the slices associated with the PH refers to.

ph_cc_alf_cr_aps_id specifies the adaptation_parameter_set_id of the ALF APS that the Cr colour component of the slices associated with the PH refers to.

7.4.8.1General Slice Header Semantics

slice_num_alf aps_ids_luma specifies the number of ALF APSs that the slice refers to. When slice_alf enabled_flag is equal to 1 and slice_num_alf aps_ids_luma is not present, the value of slice_num_alf aps_ids_luma is inferred to be equal to the value of ph_num_alf aps_ids_luma.

s

slice_alf_aps_id_luma[i] specifies the adaptation_parameter_set_id of the i-th ALF APS that the luma component of the slice refers to. The TemporalId of the APS NAL unit having aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_alf_aps_id_luma[i] shall be less than or equal to the TemporalId of the coded slice NAL unit. When slice_alf enabled_flag is equal to 1 and slice_alf_aps_id_luma[i] is not present, the value of slice_alf_aps_id_luma[i] is inferred to be equal to the value of ph_alf aps_id_luma[i].

slice_alf_aps_id_chroma specifies the adaptation_parameter_set_id of the ALF APS that the chroma component of the slice refers to. The TemporalId of the APS NAL unit having aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_alf_aps_id_chroma shall be less than or equal to the TemporalId of the coded slice NAL unit. When slice_alf enabled_flag is equal to 1 and slice_alf_aps_id_chroma is not present, the value of slice_alf_aps_id_chroma is inferred to be equal to the value of ph_alf aps_id_chroma.

slice_cc_alf cb_aps_id specifies the adaptation_parameter_set_id that the Cb colour component of the slice refers to. The TemporalId of the APS NAL unit having aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_cc_alf cb_aps_id shall be less than or equal to the TemporalId of the coded slice NAL unit. When slice_cc_alf cb_enabled_flag is equal to 1 and slice_cc_alf cb_aps_id is not present, the value of slice_cc_alf cb_aps_id is inferred to be equal to the value of ph_cc_alf_cb_aps_id.

The value of alf cc_cb_filtersignal_flag of the APS NAL unit having aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_cc_alf cb_aps_id shall be equal to 1. slice_cc_alf cr_aps_id specifies the adaptation_parameter_set_id that the Cr colour component of the slice refers to. The TemporalId of the APS NAL unit having aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_cc_alf cr_aps_id shall be less than or equal to the TemporalId of the coded slice NAL unit. When slice_cc_alf cr_enabled_flag is equal to 1 and slice_cc_alf cr_aps_id is not present, the value of slice_cc_alf cr_aps_id is inferred to be equal to the value of ph_cc_alf_cr_aps_id.

The value of alf cc_cr_filter_signal_flag of the APS NAL unit having aps_params_type equal to ALF_APS and adaptation_parameter_set_id equal to slice_cc_alf cr_aps_id shall be equal to 1. In above examples, the following may be used instead: adaptation_parameter_set_id provides an identifier for the APS for reference by other syntax elements. The length of the syntax element adaptation_parameter_set_id, in bits, is aps_params_type=ALF_APS ? M: (aps_params_type==LMCS_APS ? 2:3) wherein M is equal to a value no smaller than 3 (e.g., 4, 5, 6, 7, 8, 9). The value of ‘200, 64, 64’ may be replaced by other non-zero integer values. The value of ‘327’ may be replaced by other non-zero integer values.

6.4. Fourth Embodiment

In this embodiment, some examples on how to constrain the collocated reference picture are provided.

sh_collocated_from_10_flag equal to 1 specifies that the collocated picture used for temporal motion vector prediction is derived from reference picture list 0. sh_collocated_from_10_flag equal to 0 specifies that the collocated picture used for temporal motion vector prediction is derived from reference picture list 1. When sh_slice_type is equal to B or P, ph_temporal_mvp_enabled_flag is equal to 1, and sh_collocated_from_10_flag is not present, the following applies:

-   If sh_slice_type is equal to B, sh_collocated_from_10_flag is     inferred to be equal to ph_collocated_from_10_flag. -   Otherwise (sh_slice_type is equal to P), the value of     sh_collocated_from_10_flag is inferred to be equal to 1.     sh_collocated_ref_idx specifies the reference index of the     collocated picture used for temporal motion vector prediction.     When sh_slice_type is equal to P or when sh_slice_type is equal to B     and sh_collocated_from_10_flag is equal to 1, sh_collocated_ref_idx     refers to an entry in reference picture list 0, and the value of     sh_collocated_ref_idx shall be in the range of 0 to     NumRefldxActive[0]— 1, inclusive.     When sh_slice_type is equal to B and sh_collocated_from_10_flag is     equal to 0, sh_collocated_ref_idx refers to an entry in reference     picture list 1, and the value of sh_collocated_ref_idx shall be in     the range of 0 to NumRefldxActive[1]— 1, inclusive.     When sh_collocated_ref_idx is not present, the following applies: -   If pps_rpl_info_in_ph_flag is equal to 1, the value of     sh_collocated_ref_idx is inferred to be equal to     ph_collocated_ref_idx. -   Otherwise (pps_rpl_info_in_ph_flag is equal to 0), the value of     sh_collocated_ref_idx is inferred to be equal to 0.     It is a requirement of bitstream conformance that the picture     referred to by sh_collocated_ref_idx shall be the same for all     slices of a coded picture and     RprConstraintsActive[sh_collocated_from_10_flag ?     0:1][sh_collocated_ref_idx] shall be equal to 0     NOTE—The above constraint requires the collocated picture to have     the same spatial resolution and the same scaling window offsets     as the current picture.

FIG. 5 is a block diagram showing an example video processing system 1900 in which various techniques disclosed herein may be implemented. Various implementations may include some or all of the components of the system 1900. The system 1900 may include input 1902 for receiving video content. The video content may be received in a raw or uncompressed format, e.g., 8 or 10 bit multi-component pixel values, or may be in a compressed or encoded format. The input 1902 may represent a network interface, a peripheral bus interface, or a storage interface. Examples of network interface include wired interfaces such as Ethernet, passive optical network (PON), etc. and wireless interfaces such as Wi-Fi or cellular interfaces.

The system 1900 may include a coding component 1904 that may implement the various coding or encoding methods described in the present document. The coding component 1904 may reduce the average bitrate of video from the input 1902 to the output of the coding component 1904 to produce a coded representation of the video. The coding techniques are therefore sometimes called video compression or video transcoding techniques. The output of the coding component 1904 may be either stored, or transmitted via a communication connected, as represented by the component 1906. The stored or communicated bitstream (or coded) representation of the video received at the input 1902 may be used by the component 1908 for generating pixel values or displayable video that is sent to a display interface 1910. The process of generating user-viewable video from the bitstream representation is sometimes called video decompression. Furthermore, while certain video processing operations are referred to as “coding” operations or tools, it will be appreciated that the coding tools or operations are used at an encoder and corresponding decoding tools or operations that reverse the results of the coding will be performed by a decoder.

Examples of a peripheral bus interface or a display interface may include universal serial bus (USB) or high definition multimedia interface (HDMI) or Displayport, and so on. Examples of storage interfaces include SATA (serial advanced technology attachment), PCI, IDE interface, and the like. The techniques described in the present document may be embodied in various electronic devices such as mobile phones, laptops, smartphones or other devices that are capable of performing digital data processing and/or video display.

FIG. 6 is a block diagram of a video processing apparatus 3600. The apparatus 3600 may be used to implement one or more of the methods described herein. The apparatus 3600 may be embodied in a smartphone, tablet, computer, Internet of Things (IoT) receiver, and so on. The apparatus 3600 may include one or more processors 3602, one or more memories 3604 and video processing hardware 3606. The processor(s) 3602 may be configured to implement one or more methods described in the present document. The memory (memories) 3604 may be used for storing data and code used for implementing the methods and techniques described herein. The video processing hardware 3606 may be used to implement, in hardware circuitry, some techniques described in the present document.

FIG. 8 is a block diagram that illustrates an example video coding system 100 that may utilize the techniques of this disclosure.

As shown in FIG. 8 , video coding system 100 may include a source device 110 and a destination device 120. Source device 110 generates encoded video data which may be referred to as a video encoding device. Destination device 120 may decode the encoded video data generated by source device 110 which may be referred to as a video decoding device.

Source device 110 may include a video source 112, a video encoder 114, and an input/output (I/O) interface 116.

Video source 112 may include a source such as a video capture device, an interface to receive video data from a video content provider, and/or a computer graphics system for generating video data, or a combination of such sources. The video data may comprise one or more pictures. Video encoder 114 encodes the video data from video source 112 to generate a bitstream. The bitstream may include a sequence of bits that form a coded representation of the video data. The bitstream may include coded pictures and associated data. The coded picture is a coded representation of a picture. The associated data may include sequence parameter sets, picture parameter sets, and other syntax structures. I/O interface 116 may include a modulator/demodulator (modem) and/or a transmitter. The encoded video data may be transmitted directly to destination device 120 via I/O interface 116 through network 130 a. The encoded video data may also be stored onto a storage medium/server 130 b for access by destination device 120.

Destination device 120 may include an I/O interface 126, a video decoder 124, and a display device 122.

I/O interface 126 may include a receiver and/or a modem. I/O interface 126 may acquire encoded video data from the source device 110 or the storage medium/ server 130 b. Video decoder 124 may decode the encoded video data. Display device 122 may display the decoded video data to a user. Display device 122 may be integrated with the destination device 120, or may be external to destination device 120 which be configured to interface with an external display device.

Video encoder 114 and video decoder 124 may operate according to a video compression standard, such as the High Efficiency Video Coding (HEVC) standard, Versatile Video Coding(VVM) standard and other current and/or further standards.

FIG. 9 is a block diagram illustrating an example of video encoder 200, which may be video encoder 114 in the system 100 illustrated in FIG. 8 .

Video encoder 200 may be configured to perform any or all of the techniques of this disclosure. In the example of FIG. 9 , video encoder 200 includes a plurality of functional components. The techniques described in this disclosure may be shared among the various components of video encoder 200. In some examples, a processor may be configured to perform any or all of the techniques described in this disclosure.

The functional components of video encoder 200 may include a partition unit 201, a predication unit 202 which may include a mode select unit 203, a motion estimation unit 204, a motion compensation unit 205 and an intra prediction unit 206, a residual generation unit 207, a transform unit 208, a quantization unit 209, an inverse quantization unit 210, an inverse transform unit 211, a reconstruction unit 212, a buffer 213, and an entropy encoding unit 214.

In other examples, video encoder 200 may include more, fewer, or different functional components. In an example, predication unit 202 may include an intra block copy (IBC) unit. The IBC unit may perform predication in an IBC mode in which at least one reference picture is a picture where the current video block is located.

Furthermore, some components, such as motion estimation unit 204 and motion compensation unit 205 may be highly integrated, but are represented in the example of FIG. 9 separately for purposes of explanation.

Partition unit 201 may partition a picture into one or more video blocks. Video encoder 200 and video decoder 300 may support various video block sizes.

Mode select unit 203 may select one of the coding modes, intra or inter, e.g., based on error results, and provide the resulting intra- or inter-coded block to a residual generation unit 207 to generate residual block data and to a reconstruction unit 212 to reconstruct the encoded block for use as a reference picture. In some example, Mode select unit 203 may select a combination of intra and inter predication (CIIP) mode in which the predication is based on an inter predication signal and an intra predication signal. Mode select unit 203 may also select a resolution for a motion vector (e.g., a sub-pixel or integer pixel precision) for the block in the case of inter-predication.

To perform inter prediction on a current video block, motion estimation unit 204 may generate motion information for the current video block by comparing one or more reference frames from buffer 213 to the current video block. Motion compensation unit 205 may determine a predicted video block for the current video block based on the motion information and decoded samples of pictures from buffer 213 other than the picture associated with the current video block.

Motion estimation unit 204 and motion compensation unit 205 may perform different operations for a current video block, for example, depending on whether the current video block is in an I slice, a P slice, or a B slice.

In some examples, motion estimation unit 204 may perform uni-directional prediction for the current video block, and motion estimation unit 204 may search reference pictures of list 0 or list 1 for a reference video block for the current video block. Motion estimation unit 204 may then generate a reference index that indicates the reference picture in list 0 or list 1 that contains the reference video block and a motion vector that indicates a spatial displacement between the current video block and the reference video block. Motion estimation unit 204 may output the reference index, a prediction direction indicator, and the motion vector as the motion information of the current video block. Motion compensation unit 205 may generate the predicted video block of the current block based on the reference video block indicated by the motion information of the current video block.

In other examples, motion estimation unit 204 may perform bi-directional prediction for the current video block, motion estimation unit 204 may search the reference pictures in list 0 for a reference video block for the current video block and may also search the reference pictures in list 1 for another reference video block for the current video block. Motion estimation unit 204 may then generate reference indexes that indicate the reference pictures in list 0 and list 1 containing the reference video blocks and motion vectors that indicate spatial displacements between the reference video blocks and the current video block. Motion estimation unit 204 may output the reference indexes and the motion vectors of the current video block as the motion information of the current video block. Motion compensation unit 205 may generate the predicted video block of the current video block based on the reference video blocks indicated by the motion information of the current video block.

In some examples, motion estimation unit 204 may output a full set of motion information for decoding processing of a decoder.

In some examples, motion estimation unit 204 may do not output a full set of motion information for the current video. Rather, motion estimation unit 204 may signal the motion information of the current video block with reference to the motion information of another video block. For example, motion estimation unit 204 may determine that the motion information of the current video block is sufficiently similar to the motion information of a neighboring video block.

In one example, motion estimation unit 204 may indicate, in a syntax structure associated with the current video block, a value that indicates to the video decoder 300 that the current video block has the same motion information as the another video block.

In another example, motion estimation unit 204 may identify, in a syntax structure associated with the current video block, another video block and a motion vector difference (MVD). The motion vector difference indicates a difference between the motion vector of the current video block and the motion vector of the indicated video block. The video decoder 300 may use the motion vector of the indicated video block and the motion vector difference to determine the motion vector of the current video block.

As discussed above, video encoder 200 may predictively signal the motion vector. Two examples of predictive signaling techniques that may be implemented by video encoder 200 include advanced motion vector predication (AMVP) and merge mode signaling.

Intra prediction unit 206 may perform intra prediction on the current video block. When intra prediction unit 206 performs intra prediction on the current video block, intra prediction unit 206 may generate prediction data for the current video block based on decoded samples of other video blocks in the same picture. The prediction data for the current video block may include a predicted video block and various syntax elements.

Residual generation unit 207 may generate residual data for the current video block by subtracting (e.g., indicated by the minus sign) the predicted video block(s) of the current video block from the current video block. The residual data of the current video block may include residual video blocks that correspond to different sample components of the samples in the current video block.

In other examples, there may be no residual data for the current video block for the current video block, for example in a skip mode, and residual generation unit 207 may not perform the subtracting operation.

Transform processing unit 208 may generate one or more transform coefficient video blocks for the current video block by applying one or more transforms to a residual video block associated with the current video block.

After transform processing unit 208 generates a transform coefficient video block associated with the current video block, quantization unit 209 may quantize the transform coefficient video block associated with the current video block based on one or more quantization parameter (QP) values associated with the current video block.

Inverse quantization unit 210 and inverse transform unit 211 may apply inverse quantization and inverse transforms to the transform coefficient video block, respectively, to reconstruct a residual video block from the transform coefficient video block. Reconstruction unit 212 may add the reconstructed residual video block to corresponding samples from one or more predicted video blocks generated by the predication unit 202 to produce a reconstructed video block associated with the current block for storage in the buffer 213.

After reconstruction unit 212 reconstructs the video block, loop filtering operation may be performed reduce video blocking artifacts in the video block.

Entropy encoding unit 214 may receive data from other functional components of the video encoder 200. When entropy encoding unit 214 receives the data, entropy encoding unit 214 may perform one or more entropy encoding operations to generate entropy encoded data and output a bitstream that includes the entropy encoded data.

FIG. 10 is a block diagram illustrating an example of video decoder 300 which may be video decoder 114 in the system 100 illustrated in FIG. 8 .

The video decoder 300 may be configured to perform any or all of the techniques of this disclosure. In the example of FIG. 10 , the video decoder 300 includes a plurality of functional components. The techniques described in this disclosure may be shared among the various components of the video decoder 300. In some examples, a processor may be configured to perform any or all of the techniques described in this disclosure.

In the example of FIG. 10 , video decoder 300 includes an entropy decoding unit 301, a motion compensation unit 302, an intra prediction unit 303, an inverse quantization unit 304, an inverse transformation unit 305 , and a reconstruction unit 306 and a buffer 307. Video decoder 300 may, in some examples, perform a decoding pass generally reciprocal to the encoding pass described with respect to video encoder 200 (FIG. 9 ).

Entropy decoding unit 301 may retrieve an encoded bitstream. The encoded bitstream may include entropy coded video data (e.g., encoded blocks of video data). Entropy decoding unit 301 may decode the entropy coded video data, and from the entropy decoded video data, motion compensation unit 302 may determine motion information including motion vectors, motion vector precision, reference picture list indexes, and other motion information. Motion compensation unit 302 may, for example, determine such information by performing the AMVP and merge mode.

Motion compensation unit 302 may produce motion compensated blocks, possibly performing interpolation based on interpolation filters. Identifiers for interpolation filters to be used with sub-pixel precision may be included in the syntax elements.

Motion compensation unit 302 may use interpolation filters as used by video encoder 200 during encoding of the video block to calculate interpolated values for sub-integer pixels of a reference block. Motion compensation unit 302 may determine the interpolation filters used by video encoder 200 according to received syntax information and use the interpolation filters to produce predictive blocks.

Motion compensation unit 302 may uses some of the syntax information to determine sizes of blocks used to encode frame(s) and/or slice(s) of the encoded video sequence, partition information that describes how each macroblock of a picture of the encoded video sequence is partitioned, modes indicating how each partition is encoded, one or more reference frames (and reference frame lists) for each inter-encoded block, and other information to decode the encoded video sequence.

Intra prediction unit 303 may use intra prediction modes for example received in the bitstream to form a prediction block from spatially adjacent blocks. Inverse quantization unit 303 inverse quantizes, e.g., de-quantizes, the quantized video block coefficients provided in the bitstream and decoded by entropy decoding unit 301. Inverse transform unit 303 applies an inverse transform.

Reconstruction unit 306 may sum the residual blocks with the corresponding prediction blocks generated by motion compensation unit 202 or intra-prediction unit 303 to form decoded blocks. If desired, a deblocking filter may also be applied to filter the decoded blocks in order to remove blockiness artifacts. The decoded video blocks are then stored in buffer 307, which provides reference blocks for subsequent motion compensation/intra predication and also produces decoded video for presentation on a display device.

A listing of solutions preferred by some embodiments is provided next.

The following solutions show example embodiments of techniques discussed in the previous section (e.g., item 1).

1. A video processing method (e.g., method 700 shown in FIG. 7 ), comprising: performing (702) a conversion between a video comprising one or more video pictures, wherein the coded representation conforms to a format rule; wherein the format rule specifies that two or more syntax fields in a sequence parameter set controls a reference picture resolution (RPR) change in the video.

2. The method of solution 1, wherein a first syntax field of the two or more syntax fields indicates whether the RPR is used for one or more pictures and a second syntax field of the two or more syntax fields indicates whether a picture resolution is allowed to change in the coded representation at a sequence level.

The following solutions show example embodiments of techniques discussed in the previous section (e.g., item 2).

3. A video processing method, comprising: performing a conversion between a video comprising one or more video pictures, wherein the coded representation conforms to a format rule; wherein the format rule specifies that a single syntax field in a sequence parameter set controls a reference picture resolution (RPR) change in the video; and wherein, the format rule specifies that, irrespective of a value of the single syntax field, resampling of an inter-layer reference picture is permitted for the conversion.

The following solutions show example embodiments of techniques discussed in the previous section (e.g., items 3, 5, 6, 7, 9, 10).

4. A video processing method, comprising: performing a conversion between a video comprising one or more layers comprising one or more video pictures comprising one or more subpictures, wherein the coded representation conforms to a format rule; wherein the format rule specifies a first constraint on a cross-layer alignment or a second constraint on a combination of subpictures and scalability of inter-layer pictures.

5. The method of solution 4, wherein the first constraint defines a cross-layer alignment restriction on a current layer and all higher layers that depend on the current layer without imposing an alignment restriction on lower layers of the current layer and all higher layers that do not depend on the current layer.

6. The method of solution 4, wherein the second constraint imposes a cross-layer alignment restriction on all layers in each dependency tree of a particular layer.

7. The method of solution 4, wherein the second constraints restrictions a value of subpic_treated_as_pic_flag[i] according to a cross-layer alignment restriction.

8. The method of solution 4, wherein the second constraints restrictions a value of loop filter across subpic enabled flag[i] according to a cross-layer alignment restriction.

9. The method of any of solutions 4 to 8, wherein the first constraint and/or the second constraint are specified for a target set of access units.

10. The method of solution 4, wherein the second constraints restrictions a value of each of the scaling window parameters scaling_win_left_offset, scaling_win_right_offset, scaling_win_top_offset, and scaling_win_bottom offset according to a cross-layer alignment restriction.

The following solutions show example embodiments of techniques discussed in the previous section (e.g., item 11).

11. A video processing method, comprising: performing a conversion between a video comprising one or more layers comprising one or more video pictures comprising one or more subpictures, wherein the conversion conforms to a format rule that specifies that an inter-layer reference picture or a long term reference picture is disallowed from being a collocated picture of a current picture for the conversion.

The following solutions show example embodiments of techniques discussed in the previous section (e.g., item 12).

12. A video processing method, comprising: performing a conversion between a video comprising multiple pictures and a coded representation of the video, wherein the conversion conforms to a rule that specifies that values of each of scaling_win_left_offset, scaling_win_right_offset, scaling_win_top_offset, and scaling_win_bottom_offset are same for any two pictures within a same coded layer video sequence or coded video sequence having the same values of pic width in luma samples and pic_height_in_luma_samples.

The following solutions show example embodiments of techniques discussed in the previous section (e.g., item 13).

13. A video processing method, comprising: performing a conversion between a video comprising multiple pictures and a coded representation of the video, wherein the conversion conforms to a rule that specifies that in case that a picture resolution or a scaling window is different for a current picture and other picture in a same access unit, then inter-layer prediction is only allowed when the current picture is an intra random access point picture.

The following solutions show example embodiments of techniques discussed in the previous section (e.g., item 20).

14. A method of video processing, comprising: determining, for a conversion between video blocks of a current picture of a video and a coded represenation of the video, whether a rule is to be applied based on a first size of the video blocks compared to a second size of video blocks in a collocated video picture or an inter-layer picture, and performing the conversion based on the determining.

15. The method of solution 14, wherein the rule specifies that when the first size is greater than the second size, use of motion information from a different picture is disabled for use in the conversion in the current picture.

16. The method of solution 14, wherein the rule specifies that when the first size is greater than the second size, use of motion information from a different picture is disabled for use in the conversion in the current picture.

In the above solutions, the video blocks may correspond to a coding tree unit or a coding tree block.

17. The method of any of solutions 1 to 16, wherein the conversion comprises encoding the video into the coded representation.

18. The method of any of solutions 1 to 16, wherein the conversion comprises decoding the coded representation to generate pixel values of the video.

19. A video decoding apparatus comprising a processor configured to implement a method recited in one or more of solutions 1 to 18.

20. A video encoding apparatus comprising a processor configured to implement a method recited in one or more of solutions 1 to 18.

21. A computer program product having computer code stored thereon, the code, when executed by a processor, causes the processor to implement a method recited in any of solutions 1 to 18.

22. A method, apparatus or system described in the present document.

FIG. 13 is a flowchart representation of a method 1300 for video processing in accordance with the present technology. The method 1300 includes, at operation 1310, performing a conversion between a video unit of a current picture of a video and a bitstream of the video according to a rule. The rule specifies that, for a given picture to be available as a reference picture whose motion information is used for the conversion, the given picture has a same coding tree unit size or a same coding tree block size as the current picture.

In some embodiments, the rule specifies that a coding tool that uses the motion information is disabled in response to the given picture having a different coding tree unit size or a different coding tree block size. In some embodiments, the video unit comprises a slice. In some embodiments, the motion information is used for temporal motion vector prediction. In some embodiments, the motion information is used for sub-block based temporal motion vector prediction.

In some embodiments, the given picture is a collocated picture. In some embodiments, the collocated picture is identified by a list of collocated pictures and an index that specifies a reference index of the collocated picture used for the temporal motion vector prediction. In some embodiments, the list of collocated pictures is determined by a first syntax flag specifying whether the collocated picture used for the temporal motion vector prediction is derived from a reference picture list 0 or a reference picture list 1. In some embodiments, the first syntax flag is represented as sh_collocated_from_10_flag, and the reference index is represented as sh_collocated_ref_idx. In some embodiments, the coding tree unit size of the collocated picture is represented by a variable in a sequence parameter set that specifies a size of each coding tree unit. In some embodiments, the variable is represented as sps_log2_ctu_size_minus5.

In some embodiments, the given picture is an inter-layer picture. In some embodiments, a second syntax flag in a picture header specifies that usage of the motion information is disabled. In some embodiments, the second syntax flag is represented as ph temporal mvp enabled flag.

In some embodiments, whether and how a coding tool that uses the motion information is used for the conversion is based on coding tree unit sizes of reference pictures in one or more reference picture lists of the video unit. In some embodiments, the coding tool is disabled in response to all reference pictures having different coding tree unit sizes or different coding tree block sizes than the current picture.

In some embodiments, the conversion comprises encoding the video into the bitstream. In some embodiments, the conversion comprises decoding the video from the bitstream.

In the solutions described herein, an encoder may conform to the format rule by producing a coded representation according to the format rule. In the solutions described herein, a decoder may use the format rule to parse syntax elements in the coded representation with the knowledge of presence and absence of syntax elements according to the format rule to produce decoded video.

In the present document, the term “video processing” may refer to video encoding, video decoding, video compression or video decompression. For example, video compression algorithms may be applied during conversion from pixel representation of a video to a corresponding bitstream representation or vice versa. The bitstream representation of a current video block may, for example, correspond to bits that are either co-located or spread in different places within the bitstream, as is defined by the syntax. For example, a macroblock may be encoded in terms of transformed and coded error residual values and also using bits in headers and other fields in the bitstream. Furthermore, during conversion, a decoder may parse a bitstream with the knowledge that some fields may be present, or absent, based on the determination, as is described in the above solutions. Similarly, an encoder may determine that certain syntax fields are or are not to be included and generate the coded representation accordingly by including or excluding the syntax fields from the coded representation.

The disclosed and other solutions, examples, embodiments, modules and the functional operations described in this document can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this document and their structural equivalents, or in combinations of one or more of them. The disclosed and other embodiments can be implemented as one or more computer program products, e.g., one or more modules of computer program instructions encoded on a computer readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more them. The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.

A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this document can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read only memory or a random-access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks. However, a computer need not have such devices. Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

While this patent document contains many specifics, these should not be construed as limitations on the scope of any subject matter or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular techniques. Certain features that are described in this patent document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Moreover, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.

Only a few implementations and examples are described and other implementations, enhancements and variations can be made based on what is described and illustrated in this patent document. 

1. A method of processing video data, comprising: performing a conversion between a video unit of a current picture of a video and a bitstream of the video according to a rule, wherein the rule specifies that, for a given picture to be available as a collocated reference picture whose motion information is used for the conversion, the given picture has a same coding tree unit size or a same coding tree block size as the current picture.
 2. The method of claim 1, wherein the rule specifies that a coding tool that uses the motion information is disabled in response to the given picture having a different coding tree unit size or a different coding tree block size.
 3. The method of claim 2, wherein the coding tool is a temporal motion vector prediction coding tool or a subblock-based temporal motion vector prediction coding tool.
 4. The method of claim 1, wherein the video unit is a slice.
 5. The method of claim 1, wherein the collocated reference picture is identified by a list of collocated reference pictures and an index that specifies a reference index of the collocated reference picture.
 6. The method of claim 5, wherein the list of collocated reference pictures is determined by a first syntax flag specifying whether the collocated reference picture is derived from a reference picture list 0 or a reference picture list
 1. 7. The method of claim 6, wherein the first syntax flag is represented as sh_collocated_from_10_flag, and wherein the reference index is represented as sh_collocated_ref_idx.
 8. The method of claim 7, wherein a value of a second syntax element that specifies a size of each coding tree unit for the collocated reference picture referred to by the reference index is equal to a value of a third syntax element that specifies a size of each coding tree unit for the current picture.
 9. The method of claim 8, wherein the second syntax element and the third syntax element are included in a sequence parameter set and are represented as sps_log2_ctu_size_minus5.
 10. The method of claim 1, wherein when a fourth syntax flag in a picture header specifies that usage of the motion information is disabled, a first syntax flag specifying whether the collocated reference picture is derived from a reference picture list 0 or a reference picture list 1 and a reference index of the collocated reference picture are omitted from the bitstream.
 11. The method of claim 10, wherein the fourth syntax flag is represented as ph temporal mvp enabled flag.
 12. The method of claim 10, wherein the first syntax flag is represented as sh_collocated_from_10_flag or ph_collocated_from_10_flag, and wherein the reference index is represented as sh_collocated_ref_idx or ph_collocated_ref_idx.
 13. The method of claim 1, wherein the conversion comprises encoding the video into the bitstream.
 14. The method of claim 1, wherein the conversion comprises decoding the video from the bitstream.
 15. An apparatus for processing video data comprising a processor and a non-transitory memory with instructions thereon, wherein the instructions upon execution by the processor, cause the processor to: perform a conversion between a video unit of a current picture of a video and a bitstream of the video according to a rule, wherein the rule specifies that, for a given picture to be available as a collocated reference picture whose motion information is used for the conversion, the given picture has a same coding tree unit size or a same coding tree block size as the current picture.
 16. The method of claim 15, wherein the rule specifies that a coding tool that uses the motion information is disabled in response to the given picture having a different coding tree unit size or a different coding tree block size.
 17. A non-transitory computer-readable storage medium storing instructions that cause a processor to: perform a conversion between a video unit of a current picture of a video and a bitstream of the video according to a rule, wherein the rule specifies that, for a given picture to be available as a collocated reference picture whose motion information is used for the conversion, the given picture has a same coding tree unit size or a same coding tree block size as the current picture.
 18. The non-transitory computer-readable storage medium of claim 17, wherein the rule specifies that a coding tool that uses the motion information is disabled in response to the given picture having a different coding tree unit size or a different coding tree block size.
 19. A non-transitory computer-readable recording medium storing a bitstream of a video which is generated by a method performed by a video processing apparatus, wherein the method comprises: generating a bitstream of the video from a video unit of a current picture of the video according to a rule; storing the bitstream in a non-transitory computer-readable recording medium, wherein the rule specifies that, for a given picture to be available as a collocated reference picture whose motion information is used for the conversion, the given picture has a same coding tree unit size or a same coding tree block size as the current picture.
 20. The non-transitory computer-readable recording medium of claim 19, wherein the rule specifies that a coding tool that uses the motion information is disabled in response to the given picture having a different coding tree unit size or a different coding tree block size. 